How severe is GHSA-x96m-rh44-vgv8?

No CVSS score has been assigned to GHSA-x96m-rh44-vgv8 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-x96m-rh44-vgv8?

GHSA-x96m-rh44-vgv8 affects the following packages: org.apache.shiro:shiro-core (Maven), org.apache.shiro:shiro-core (Maven). Ecosystems affected: Maven.

How do I fix GHSA-x96m-rh44-vgv8?

Update org.apache.shiro:shiro-core to 2.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-x96m-rh44-vgv8 is resolved across your whole dependency graph.

How do I detect GHSA-x96m-rh44-vgv8 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.shiro:shiro-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-x96m-rh44-vgv8 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-x96m-rh44-vgv8 actively exploited in the wild?

No public exploit code has been indexed for GHSA-x96m-rh44-vgv8 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-x96m-rh44-vgv8?

GHSA-x96m-rh44-vgv8 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 44th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-x96m-rh44-vgv8?

GHSA-x96m-rh44-vgv8 is classified as CWE-90 (CWE-90). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-x96m-rh44-vgv8 published, and has it been updated?

GHSA-x96m-rh44-vgv8 was published on June 17, 2026 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Apache Shiro: LDAP DN Injection in DefaultLdapRealm

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-x96m-rh44-vgv8.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs44th percentile — riskier than 44% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

2 pkgs affected

☕org.apache.shiro:shiro-core☕org.apache.shiro:shiro-core

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.shiro:shiro-core`	all versions	2.2.1`org.apache.shiro:shiro-core:2.2.1`
☕Maven	`org.apache.shiro:shiro-core`	≥ 3.0.0-alpha-0&&< 3.0.0-alpha-2	3.0.0-alpha-2`org.apache.shiro:shiro-core:3.0.0-alpha-2`

Affected Products

1 product · 2 configurations

Application

shiroapache

< 2.2.1

1 version

3.0.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.shiro:shiro-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.shiro:shiro-core to 2.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-x96m-rh44-vgv8 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

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 issu

O3 Security · Impact-Aware SCA

Is GHSA-x96m-rh44-vgv8 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

Apache Shiro: LDAP DN Injection in DefaultLdapRealmGHSA-x96m-rh44-vgv8