Skip to main content
VulnerabilityPublished Updated

CVE-2026-57522: bitwarden server · Injection

Affects bitwarden serverSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 2.3 Low : upgrade to 2026.5.0 when convenient.

Data as of 7 Nov 2026, 23:24 UTC

CVSS 4.0 base score
2.3Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2026.5.0
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 7 Nov 2026.

What to do

Upgrade bitwarden server to 2026.5.0.

Affected software

ProductAffectedFixed in
bitwardenserverAffected
  • <2026.5.0
Fixed in–
GitHubserverpkg:github/serverOther threatsAffected
  • <2026.5.0
Fixed in
  • 2026.5.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Since the vulnerability affects versions prior to 2026.5.0, upgrading to version 2026.5.0 or later is likely to address the issue once an official fix is released. Until then, organizations should review event integration templates and consider restricting user-controlled tokens in templates or sanitizing user input to mitigate injection risks.

Description

Bitwarden Server before 2026.5.0 contains a JSON injection vulnerability in IntegrationTemplateProcessor.ReplaceTokens(), which substitutes user-controlled values into event-integration templates without JSON encoding. When an organization has configured an event integration whose template references a user-controlled token (such as #ActingUserName# or #UserName#, populated from a member's display name), an authenticated member can set their display name to JSON metacharacters and inject arbitrary key-value pairs into the rendered payloads delivered to webhook, SIEM, Slack, Teams, or Datadog endpoints, making injected fields indistinguishable from legitimate template output.

References

Community reviews

Loading reviews…