CVE-2026-57522: Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') in bitwarden server
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.
AI Analysis
Technical Summary
CVE-2026-57522 is a JSON injection vulnerability in Bitwarden Server before version 2026.5.0. The issue occurs in the IntegrationTemplateProcessor.ReplaceTokens() method, which inserts user-controlled tokens such as #ActingUserName# or #UserName# into event integration templates without JSON encoding. This allows an authenticated user to craft their display name with JSON metacharacters, injecting arbitrary key-value pairs into the JSON payloads delivered to various integration endpoints. This can cause downstream components to process maliciously crafted JSON fields as if they were legitimate, potentially impacting the integrity of event data.
Potential Impact
An authenticated member can inject arbitrary JSON key-value pairs into event integration payloads sent to external systems like webhook receivers, SIEM, Slack, Teams, or Datadog. This could lead to corrupted or misleading event data being processed by these systems. However, the vulnerability requires authentication and has a low CVSS score, indicating limited impact and exploitability.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. 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.
CVE-2026-57522: Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') in bitwarden server
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.
CVSS v4.0
Score 2.3low
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-57522 is a JSON injection vulnerability in Bitwarden Server before version 2026.5.0. The issue occurs in the IntegrationTemplateProcessor.ReplaceTokens() method, which inserts user-controlled tokens such as #ActingUserName# or #UserName# into event integration templates without JSON encoding. This allows an authenticated user to craft their display name with JSON metacharacters, injecting arbitrary key-value pairs into the JSON payloads delivered to various integration endpoints. This can cause downstream components to process maliciously crafted JSON fields as if they were legitimate, potentially impacting the integrity of event data.
Potential Impact
An authenticated member can inject arbitrary JSON key-value pairs into event integration payloads sent to external systems like webhook receivers, SIEM, Slack, Teams, or Datadog. This could lead to corrupted or misleading event data being processed by these systems. However, the vulnerability requires authentication and has a low CVSS score, indicating limited impact and exploitability.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. 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.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-06-24T15:58:58.537Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a3d89044853345fc16510b9
Added to database: 06/25/2026, 20:01:08 UTC
Last enriched: 07/15/2026, 10:19:00 UTC
Last updated: 08/08/2026, 18:05:45 UTC
Views: 103
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.