CVE-2026-48188
Unauthenticated SQL injection in OTRS CE DB layer enables bypass auth (NO_BACKSLASH_ESCAPES).
Is CVE-2026-48188 being exploited?
Not confirmed. CVE-2026-48188 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.74% probability of exploitation in the next 30 days.
How severe is CVE-2026-48188?
CVE-2026-48188 is rated Critical with a CVSS score of 9.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-48188?
Yes. A fix has been recorded for CVE-2026-48188. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-48188 affect?
CVE-2026-48188 affects OTRS Community Edition 6.0.x, OTRS 7.0.x, OTRS 8.0.x, OTRS 2023.x, and 3 further products or versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-48188?
Patch to 2026.4.x+ and verify NO_BACKSLASH_ESCAPES config.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Auth bypass via unauthenticated SQL injection; attacker can read/modify data in OTRS CE DB when NO_BACKSLASH_ESCAPES is enabled.
Immediate action required
- affected7.0.x
- affected8.0.x
- affected2023.x
- affected2024.x
- affected2025.x
- affected>= 2026.x and <= 2026.3.x
- affected6.x
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.