Cyber Resilience

CVE-2026-49268

Apache Shiro ≤ 2.2.1

Published
17 June 2026
Modified
18 June 2026
Patch / advisory
View advisory
CVSS Score v4 8.8
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:P/AU:Y/R:A/V:X/RE:L/U:Red
EPSS Score 0.0049 40th percentile
Risk Priority 45 floored blend · peak EPSS

Summary

CVE-2026-49268 is a high-severity LDAP Injection (CWE-90) vulnerability in Apache Shiro. Its CVSS base score is 8.8 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 40th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A05:2025 Injection

EU & UK References

Vulnerability Data

A remote attacker can inject LDAP special characters into the Distinguished Name (DN) construction in DefaultLdapRealm class. User-supplied username input is directly concatenated into the LDAP DN template without any escaping of RFC 2253 special characters. This allows an attacker…

more

to manipulate the DN structure used for LDAP bind authentication, potentially bypassing authentication or impersonating other users. This issue affects all Apache Shiro versions through 2.2.0, and 3.0.0-alpha-1 when using DefaultLdapRealm Upgrade to Apache Shiro 2.2.1 or 3.0.0-alpha-2 or later, which fixes the issue.

CWE(s)
CWE-90

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-34478Same product: Apache Shiro
CVE-2026-23903Same product: Apache Shiro
CVE-2023-46749Same product: Apache Shiro
CVE-2026-44598Same product: Apache Shiro
CVE-2020-17523Same product: Apache Shiro
CVE-2023-46750Same product: Apache Shiro
CVE-2026-43827Same product: Apache Shiro
CVE-2026-48589Same product: Apache Shiro
CVE-2026-23901Same product: Apache Shiro
CVE-2026-41919Same vendor: Apache

Affected Assets

apache
shiro
3.0.0 · ≤ 2.2.1

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.2.6

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation can discover LDAP injection flaws through static analysis or crafted test cases.

SI-10 Information Input Validation good match

Input validation directly stops untrusted data from reaching an LDAP query builder without neutralization of special characters.

SA-8 Security and Privacy Engineering Principles partial match

Secure engineering principles require safe query construction and escaping that structurally prevents LDAP injection.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require input neutralization and query parameterization to prevent LDAP injection.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development catches LDAP injection via dynamic analysis or fuzzing, but does not prevent it at the source.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle mandates input validation and query construction practices that directly prevent LDAP injection.

A.8.26 Application security requirements partial match
prevents

Application security requirements include explicit rules for safe construction of directory queries, mitigating LDAP injection.

A.8.28 Secure coding partial match
prevents

Secure coding standards require proper neutralization of LDAP special characters, directly eliminating this weakness.

A.8.27 Secure system architecture and engineering principles none match
mitigates

Secure architecture principles encourage safe query interfaces but do not prescribe the specific coding controls needed for LDAP injection.

A.8.3 Information access restriction none match
none

Information access restriction limits who can query LDAP but does not address how queries are built.

References