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 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.

There are packages installed that are affected by a vulnerability referenced in the following CVE:

  - 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 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.
    (CVE-2026-49268)

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - 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 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.
    (CVE-2026-49268)

Note that Nessus relies on the presence of the package as reported by the vendor.

ID	Name	Product	Family	Type	Severity
460259	Echo: org.apache.shiro:shiro-core: security update to 2.2.1	Tenable Cloud Security	Echo Local Security Checks	Local	high
460259	Echo: org.apache.shiro:shiro-core: security update to 2.2.1	Tenable Self-Hosted Container Security	Echo Local Security Checks	Local	high
321744	Linux Distros Unpatched Vulnerability : CVE-2026-49268	Nessus	Misc.	Local	high
443524	SCA: security update for org.apache.shiro:shiro-core (GHSA-x96m-rh44-vgv8)	Tenable Cloud Security	SCA Checks	Local	high
443524	SCA: security update for org.apache.shiro:shiro-core (GHSA-x96m-rh44-vgv8)	Tenable Self-Hosted Container Security	SCA Checks	Local	high

Detections

Analytics

CVE-2026-49268

high

Tenable Plugins

high

high

high

high

high