BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-49268High confidence

Apache Shiro: LDAP DN Injection in DefaultLdapRealm

Apache Software Foundation · Apache Shiro

8.8HighCVSS 4.0
Recommended action
Within 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Fix not verified
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:High, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 0.76% for the current model date.

Compensating controls

  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Apache Software Foundation Apache Shiro and falls inside the recorded affected range.
  2. Recheck the vendor advisory before scheduling a change because no verified fixed version is currently retained.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 30 daysRemediation target: Within 180 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

5 package states
Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourceshiroAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourceshiroAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourceshiroAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourceshiroAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · esm-appsshiroUnder evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Open-source package ranges4 source-attributed ranges

These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.

Ecosystem and packageAffected rangeFirst fixed versionEvidence
Mavenorg.apache.shiro:shiro-coreECOSYSTEM: introduced 0; fixed 2.2.12.2.1OSV record ↗aggregator derived · 10 Sep 2026
Mavenorg.apache.shiro:shiro-coreECOSYSTEM: introduced 3.0.0-alpha-0; fixed 3.0.0-alpha-23.0.0-alpha-2OSV record ↗aggregator derived · 10 Sep 2026
mavenorg.apache.shiro:shiro-core< 2.2.12.2.1GitHub advisory ↗github reviewed aggregator · 18 Jun 2026
mavenorg.apache.shiro:shiro-core>= 3.0.0-alpha-0, < 3.0.0-alpha-23.0.0-alpha-2GitHub advisory ↗github reviewed aggregator · 18 Jun 2026
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-37701

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Fix not verified
01

What, why and how

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.

What

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.

Why

The product constructs all or part of an LDAP query using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended LDAP query when it is sent to a downstream component.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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.

Why

The product constructs all or part of an LDAP query using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended LDAP query when it is sent to a downstream component.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Improper Neutralization of Special Elements used in an LDAP Query ('LDAP Injection') → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Not a CVSS 4.0 base metric
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-90 ↗

CWE-90: Improper Neutralization of Special Elements used in an LDAP Query ('LDAP Injection'). The product constructs all or part of an LDAP query using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended LDAP query when it is sent to a downstream component.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N/S:P/AU:Y/R:A/RE:L/U:Red

Common Vulnerability Scoring System 4.0: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.ATNoneAttack requirements: No additional deployment or execution condition is required.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.VCLowVulnerable-system confidentiality: A successful attack can cause a limited loss.VIHighVulnerable-system integrity: A successful attack can cause a major loss.VANoneVulnerable-system availability: No direct loss is represented by this metric.SCNoneSubsequent-system confidentiality: No direct loss is represented by this metric.SINoneSubsequent-system integrity: No direct loss is represented by this metric.SANoneSubsequent-system availability: No direct loss is represented by this metric.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-90
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

Cyber Security Agency of Singapore · English · CSA-SB-20260624Security Bulletin 24 June 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 24 June 2026, published on 24 June 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1256Multiples vulnérabilités dans les produits IBM

ecord?id=CVE-2026-45970 Référence CVE CVE-2026-45991 https://www.cve.org/CVERecord?id=CVE-2026-45991 Référence CVE CVE-2026-46120 https://www.cve.org/CVERecord?id=CVE-2026-46120 Référence CVE CVE-2026-4800 https://www.cve.org/CVERecord?id=CVE-2026-4800 Référence CVE CVE-2026-48586 https://www.cve.org/CVERecord?id=CVE-2026-48586 Référence CVE CVE-2026-4867 https://www.cve.org/CVERecord?id=CVE-2026-4867 Référence CVE CVE-2026-48801 https://www.cve.org/CVERecord?id=CVE-2026-48801 Référence CVE CVE-2026-48913 https://www.cve.org/CVERecord?id=CVE-2026-48913 Référence CVE CVE-2026-48988 https://www.cve.org/CVERecord?id=CVE-2026-48988 Référence CVE CVE-2026-49268 https://www.cve.org/CVERecord?id=CVE-2026-49268 Référence CVE CVE-2026-49356 https://www.cve.org/CVERecord?id=CVE-2026-49356 Référence CVE CVE-2026-49458 https://www.cve.org/CVERecord?id=CVE-2026-49458 Référence CVE CVE-2026-49459 https://www.cve.org/CVERecord?id=CVE-2026-49459 Référence CVE CVE-2026-49844 https://www.cve.org/CVERecord?id=CVE-2026-49844 Référence CVE CVE-2026-49975 https://www.cve.org/CVERecord?id=CVE-2026-49975 Référence CVE CVE-2026-49978 https://www.cve.org/CVERecord?id=CVE-2026-49978 Référence CVE CVE-2026-5038 https://www.cve.org/CVERecord?id=CVE-2026-5038 Référence CVE CVE-2026-5078 https://www.cve.org/CVERecord?id=CVE

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1165Multiples vulnérabilités dans les produits IBM

ord?id=CVE-2026-47885 Référence CVE CVE-2026-47887 https://www.cve.org/CVERecord?id=CVE-2026-47887 Référence CVE CVE-2026-47889 https://www.cve.org/CVERecord?id=CVE-2026-47889 Référence CVE CVE-2026-47890 https://www.cve.org/CVERecord?id=CVE-2026-47890 Référence CVE CVE-2026-47891 https://www.cve.org/CVERecord?id=CVE-2026-47891 Référence CVE CVE-2026-4800 https://www.cve.org/CVERecord?id=CVE-2026-4800 Référence CVE CVE-2026-48043 https://www.cve.org/CVERecord?id=CVE-2026-48043 Référence CVE CVE-2026-48589 https://www.cve.org/CVERecord?id=CVE-2026-48589 Référence CVE CVE-2026-48978 https://www.cve.org/CVERecord?id=CVE-2026-48978 Référence CVE CVE-2026-49268 https://www.cve.org/CVERecord?id=CVE-2026-49268 Référence CVE CVE-2026-49458 https://www.cve.org/CVERecord?id=CVE-2026-49458 Référence CVE CVE-2026-49459 https://www.cve.org/CVERecord?id=CVE-2026-49459 Référence CVE CVE-2026-49844 https://www.cve.org/CVERecord?id=CVE-2026-49844 Référence CVE CVE-2026-49978 https://www.cve.org/CVERecord?id=CVE-2026-49978 Référence CVE CVE-2026-50010 https://www.cve.org/CVERecord?id=CVE-2026-50010 Référence CVE CVE-2026-50020 https://www.cve.org/CVERecord?id=CVE-2026-50020 Référence CVE CVE-2026-50151 https://www.cve.org/CVERecord?id=CVE-2026-50151 Référence CVE CVE-2026-50162 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0986Multiples vulnérabilités dans les produits IBM

CVERecord?id=CVE-2026-47058 Référence CVE CVE-2026-47059 https://www.cve.org/CVERecord?id=CVE-2026-47059 Référence CVE CVE-2026-47063 https://www.cve.org/CVERecord?id=CVE-2026-47063 Référence CVE CVE-2026-4890 https://www.cve.org/CVERecord?id=CVE-2026-4890 Référence CVE CVE-2026-4891 https://www.cve.org/CVERecord?id=CVE-2026-4891 Référence CVE CVE-2026-4892 https://www.cve.org/CVERecord?id=CVE-2026-4892 Référence CVE CVE-2026-4893 https://www.cve.org/CVERecord?id=CVE-2026-4893 Référence CVE CVE-2026-48962 https://www.cve.org/CVERecord?id=CVE-2026-48962 Référence CVE CVE-2026-48978 https://www.cve.org/CVERecord?id=CVE-2026-48978 Référence CVE CVE-2026-49268 https://www.cve.org/CVERecord?id=CVE-2026-49268 Référence CVE CVE-2026-49432 https://www.cve.org/CVERecord?id=CVE-2026-49432 Référence CVE CVE-2026-49434 https://www.cve.org/CVERecord?id=CVE-2026-49434 Référence CVE CVE-2026-50151 https://www.cve.org/CVERecord?id=CVE-2026-50151 Référence CVE CVE-2026-50162 https://www.cve.org/CVERecord?id=CVE-2026-50162 Référence CVE CVE-2026-50163 https://www.cve.org/CVERecord?id=CVE-2026-50163 Référence CVE CVE-2026-50645 https://www.cve.org/CVERecord?id=CVE-2026-50645 Référence CVE CVE-2026-50734 https://www.cve.org/CVERecord?id=CVE-2026-50734 Référence CVE CVE-2026-53916 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-020524Apache Software FoundationのApache ShiroにおけるLDAP インジェクションの脆弱性

リモートの攻撃者がDefaultLdapRealmクラスのDistinguished Name(DN)構築時にLDAPの特殊文字を注入できます。ユーザーが入力したユーザー名はRFC 2253の特殊文字のエスケープ処理を行わずにLDAP DNテンプレートに直接連結されます。これにより、攻撃者はLDAPバインド認証に使用されるDN構造を操作でき、認証を回避したり他ユーザーになりすましたりすることが可能です。この問題は、DefaultLdapRealmを使用するすべてのApache Shiroバージョン2.2.0および3.0.0-alpha-1に影響します。問題を修正したApache Shiro 2.2.1または3.0.0-alpha-2以降にアップグレードしてください。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix not verified
Affected
Apache Shiro: ≤ 2.2.0, 3.0.0-alpha-0 ≤ 3.0.0-alpha-1
Fixed
No fixed version is explicitly recorded in the structured CVE data.
Action
No verified patch reference is present in the current structured sources. Check the vendor advisory before making a change.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 17 Jun 2026 · Last source change 17 Jun 2026, 17:02 UTC · CWE-90 · Improper Neutralization of Special Elements used in an LDAP Query ('LDAP Injection')

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-37701
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceCNA
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-49268 · cve.blacktree.nl