Skip to content
NewCybercrime Report 2026 · Eight Chapters · A Post Is Not An Incident → Explore The ChaptersCybercrime Report 2026 → Explore

Apache Shiro LDAP DN Injection (CVE-2026-49268)

CVE-2026-49268 is an LDAP Distinguished Name (DN) injection flaw in Apache Shiro's DefaultLdapRealm.

Reviewed by
Brandefense Analyst Team
Published
Reading Time
3 min read
CVE ID
CVE-2026-49268
Vendor
Apache Software Foundation
Affected Product
Apache Shiro
Exploitation
Not confirmed
Published
2026-06-17

Apache says affected installations can let a remote attacker alter the DN used for LDAP bind authentication, potentially bypassing authentication or impersonating another user. The affected range is Shiro through 2.2.0 and 3.0.0-alpha-1 when DefaultLdapRealm is used.Apache rates the issue Critical and identifies 2.2.1 or 3.0.0-alpha-2 and later as fixed. The flaw was disclosed in June 2026 and was included in Apache's November 14 advisory roundup. It is distinct from CVE-2026-129349, which concerns authentication caching on the same realm.

What it allows

How Does CVE-2026-49268 Affect LDAP Authentication?

DefaultLdapRealm concatenated a supplied username into an LDAP DN template without escaping RFC 2253 special characters. Apache says an attacker can change the resulting DN structure before the LDAP bind. Depending on the application and directory configuration, that may bypass authentication or impersonate another directory user.

The vulnerable operation is DN construction, not LDAP authentication caching. The separate Shiro LDAP caching flaw requires authenticationCachingEnabled to be true and has a different fix. Review both conditions when an application uses DefaultLdapRealm.

Apache's disclosure establishes the potential impact, not a confirmed incident at any particular installation. In the November 16, 2026 source package, a GitHub repository search returned two public results whose descriptions mention CVE-2026-49268. This count does not establish working exploit code or active exploitation.

A vulnerability intelligence platform can help prioritize this application-specific exposure alongside other fixes. The vulnerability intelligence glossary explains the evidence used in that decision.

Who is affected

Which Shiro Installations Are Affected?

Apache lists Shiro versions through 2.2.0 and the 3.0.0-alpha-1 prerelease when DefaultLdapRealm is used. Its original advisory also names 3.0.0-alpha-0. A Shiro dependency alone does not establish exposure; confirm that the running application actually configures DefaultLdapRealm for LDAP authentication.

Inventory the running shiro-core version, the realm class and the deployed LDAP configuration. Check direct and transitive dependencies, then confirm the version loaded by the running application after deployment. Because Apache gives no comparable lower boundary for every historical release, use its affected-version statement and a manual configuration check rather than an automated branch range.

Apache says Shiro v2 was superseded by v3 on June 29, 2026. The vulnerability management guide can help track the application owner, update and verification evidence.

Timeline

  1. 2026-06-17

    Apache published the CVE-2026-49268 advisory; NVD published its record on the same date.

  2. 2026-11-14

    Apache's advisory roundup again identified the affected LDAP realm and fixed versions.

What to do

  1. Identify affected LDAP realms

    Find applications that load Apache Shiro through 2.2.0 or 3.0.0-alpha-1. Confirm whether each running application uses DefaultLdapRealm for LDAP authentication; inspect configuration rather than inferring exposure from the dependency alone.

  2. Upgrade the affected Shiro line

    Upgrade affected 2.x installations to at least 2.2.1, or affected 3.x prereleases to at least 3.0.0-alpha-2. Apache's November roundup recommends the latest release and says 3.0.2 or later covers all three issues it discusses on the 3.x line.

  3. Verify the running fix

    After deployment, confirm the shiro-core version loaded by the application and that LDAP authentication still follows the intended account mapping. Record the running version, not just the build manifest or lockfile.

  4. Review related LDAP configuration

    Check whether authenticationCachingEnabled is true on DefaultLdapRealm or JndiLdapRealm. If it is, assess the separate CVE-2026-129349 and its 3.0.1 fix; the 2.2.1 fix for this CVE does not resolve that caching condition.

What Brandefense can do

Frequently Asked Questions

What is CVE-2026-49268?

It is an LDAP DN injection flaw in Apache Shiro's DefaultLdapRealm. An unescaped username can alter the DN used for LDAP bind authentication.

Does every Shiro application have this exposure?

Apache limits the issue to affected versions using DefaultLdapRealm. Check the realm configured in the running application as well as its Shiro version.

Which Shiro versions fix CVE-2026-49268?

Apache identifies 2.2.1 and 3.0.0-alpha-2 or later as fixed. Verify the version actually loaded after updating the application.

Is this the same issue as CVE-2026-129349?

No. CVE-2026-129349 is a separate flaw involving enabled LDAP authentication caching and requires its own 3.0.1 or later fix.

Sources

  1. Critical security advisories: LDAP realm and cookie fixesApache Shiro
  2. Apache Shiro Security ReportsApache Shiro
  3. CVE-2026-49268 vendor advisoryApache Shiro
  4. CVE-2026-49268 DetailNVD
ShareLinkedInX
Brandefense logo

Stay Ahead of Digital Threats.

Take control of your digital security with an exclusive demo of our AI-driven threat intelligence platform.

Open The Full Demo Form →