Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessSend crafted SVG payload via email
-
DeliveryOTRS ingests email as ticket article
-
ExploitAgent or customer opens affected ticket
-
ExecutionBrowser renders active SVG without sanitization
-
PersistUncontrolled resource consumption exhausts browser
-
ImpactDenial of service to affected user session
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V2 - Validation and Business Logic Resource consumption limits
MITRE ATT&CK
1 technique across 1 tactic: Impact The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | The attack requires that the target OTRS instance accepts inbound email and converts it into ticket articles, which is the standard deployment model for OTRS helpdesk systems. Exploitation is then triggered when an authenticated agent or customer (UI:R) opens the affected ticket in their browser - the attacker has no control over timing but can target any monitored email queue. No authentication is required from the attacker's side (PR:N per CVSS vector) - only the ability to send email to a monitored address. The CSP bypass is a key condition: environments that assumed their CSP policy prevented content injection attacks are still fully exposed. Limiting factors include the UI:R requirement (the ticket must actually be opened by a user) and the availability-only impact (no data exfiltration or code execution). The DoS is browser-scoped, not server-scoped, meaning the OTRS backend remains operational even during an attack. |
| Impact | The CVSS 3.1 base score of 6.5 (Medium) reflects a network-reachable, low-complexity attack requiring no privileges (PR:N) but needing user interaction (UI:R) to open the malicious ticket. The impact is availability-only (A:H, C:N, I:N) with unchanged scope, meaning the DoS is confined to the browser session of the user who opens the ticket rather than the server itself. No EPSS score was provided in the available intelligence, and the CVE is not listed in CISA's Known Exploited Vulnerabilities catalog, so no confirmed active exploitation is established. No POC code has been identified. In practice, this vulnerability is a realistic threat to help desk and customer portal operations: a malicious actor with the ability to submit an email to a monitored queue could force DoS conditions for every agent who opens the resulting ticket, potentially causing repeated browser crashes or slowdowns during incident handling. The CSP bypass component elevates the practical risk beyond what the CVSS score alone suggests, as defenders may incorrectly assume their CSP renders the attack moot. CVSS vector and description are consistent - no conflicting signals detected. |
| Exploit ScenarioDerived | An attacker crafts an email embedding a malicious SVG payload - such as a deeply recursive SVG filter or exponential animation element reference - and sends it to an OTRS-monitored support inbox. When a support agent or customer portal user opens the resulting ticket, their browser begins rendering the SVG, consuming excessive CPU or memory and resulting in a browser hang or crash. No public exploit code has been identified, but the technique is well-understood in SVG abuse research and does not require sophisticated tooling. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jun 01, 2026
SVG content injection in OTRS ticket article rendering enables unauthenticated remote attackers to deliver browser-side denial of service against agents and customers who open affected tickets. Specially crafted SVG payloads submitted via inbound email trigger uncontrolled resource exhaustion during rendering, without requiring JavaScript execution, and the attack vector is not blocked by the application's configured Content Security Policy - making CSP-based mitigations ineffective. No public exploit code or active exploitation has been identified at time of analysis, but the low-complexity, no-authentication-required delivery mechanism (via email) lowers the barrier to abuse significantly.
RemediationAI
The primary remediation is to upgrade OTRS to version 2026.4.X or later, which is inferred as the fixed release based on the advisory's statement that OTRS 2026.X before 2026.4.X is affected - this should be confirmed against the vendor advisory at https://otrs.com/release-notes/otrs-security-advisory-2026-07/. For ((OTRS)) Community Edition 6.x and forks, no vendor-maintained patch is available given its end-of-life status; organizations running these versions should treat migration to supported OTRS as a priority. As an immediate compensating control, administrators can configure email preprocessing rules or an upstream email gateway to strip or quarantine messages containing inline SVG attachments or base64-encoded SVG content before they are ingested as ticket articles - this eliminates the delivery vector at the cost of potentially discarding legitimate SVG-formatted correspondence. Restricting ticket access to a minimal set of trusted agents reduces the attack surface but does not eliminate the vulnerability. Do not rely solely on CSP as a control, as the advisory explicitly states it is ineffective against this attack.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The affected component is the ticket article rendering engine in OTRS and its open-source fork ((OTRS)) Community Edition, which renders email-originated content in a browser context. SVG (Scalable Vector Graphics) images support active content constructs - such as animation elements, filter primitives, and recursive references - that can trigger computationally expensive operations in the browser's rendering engine without invoking JavaScript. CWE-400 (Uncontrolled Resource Consumption) applies here: the application fails to sanitize or limit active SVG content before it is presented to users, allowing payloads that consume excessive CPU or memory during rendering. The vulnerability is notable because it circumvents the configured CSP, which typically limits script execution but does not constrain SVG rendering primitives such as feTile, feFlood, or self-referential use elements. CPE strings cpe:2.3:a:otrs_ag:otrs and cpe:2.3:a:otrs_ag:((otrs))_community_edition confirm both product lines are affected across the full wildcard version range reported.
Know when Otrs gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
Primary rating from Vendor (OTRS) · only source for this CVE.
CVSS VectorVendor: OTRS
DescriptionCVE.org
An improper neutralization of active SVG content in OTRS or ((OTRS)) Community Edition ticket article rendering allows attackers to inject specially crafted SVG payloads via email content, leading to browser-side resource exhaustion and denial of service when affected tickets are opened by an agent or customer. The issue can be exploited without JavaScript execution and is not mitigated by the configured Content Security Policy (CSP).
This issue affects OTRS:
- 7.0.X
- 8.0.X
- 2023.X
- 2024.X
- 2025.X
- 2026.X before 2026.4.X
Please note that ((OTRS)) Community Edition 6.x and before are vulnerable. Products based on the ((OTRS)) Community Edition also very likely to be affected
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
Related Vulnerabilities in OTRS Authorization, Injection, and XSS Flaws
View all 7In OTRS 6.0.x up to and including 6.0.1, OTRS 5.0.x up to and including 5.0.24, and OTRS 4.0.x up to and including 4.0.2
In the Admin Package Manager in Open Ticket Request System (OTRS) 5.0.0 through 5.0.24 and 6.0.0 through 6.0.1, authenti
Multiple cross-site request forgery (CSRF) vulnerabilities in (1) CustomerPreferences.pm, (2) CustomerTicketMessage.pm,
Open Ticket Request System (OTRS) 3.3.9 has XSS in index.pl?Action=AgentStats requests, as demonstrated by OrderBy=[XSS]
Improper Input Validation vulnerability in the upload functionality for user avatars allows functionality misuse due to
Improper Input Validation vulnerability in OTRS AG OTRS, OTRS AG ((OTRS)) Community Edition allows SQL Injection via Tic
Multiple SQL injection vulnerabilities in the FAQ package 2.x before 2.3.6, 4.x before 4.0.5, and 5.x before 5.0.5 in Op
Authentication bypass in ((OTRS)) Community Edition 6.x and earlier lets an unauthenticated remote attacker impersonate
Cross-site scripting (XSS) vulnerability in Open Ticket Request System (OTRS) Help Desk 2.4.x before 2.4.15, 3.0.x befor
OTRS fails to immediately invalidate previously issued JWT authentication tokens when an agent or customer user account
The functions to fetch e-mail via POP3 or IMAP as well as sending e-mail via SMTP use OpenSSL for static SSL or TLS base
EUVD-2026-33548
GHSA-8xg9-c63w-vfj6
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB