CVE-2026-49268

CRITICALNVD 9.19.1—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.1 under NVD CVSS v3. EPSS exploit probability: 0.5%, top 59% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.8%CVSS: 9.1Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
46
EG Risk 46/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity91% × 45%
Exploitation0% × 40%
Automatability30% × 15%
EPSS PROB
0.8%
EPSS %ILE
53rd
KEV
Not listed

Published

June 17, 2026

Last Modified

June 18, 2026

Advisory Details (2)

Auto-updated Sep 16, 2026
Patch available.
generic

oss-security - CVE-2026-49268: Apache Shiro: LDAP DN Injection in DefaultLdapRealm

http://www.openwall.com/lists/oss-security/2026/06/17/8
generic
https://lists.apache.org/thread/svszql3od8td7hn6conyj2oq70v53b5s

Vendor Advisories for CVE-2026-49268(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
shiro1.3.2-4, 1.3.2-4+deb11u1, 1.3.2-5, 1.3.2-6
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
shiro1.3.2-5, 1.3.2-6
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
shiro1.3.2-6
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
shiro1.3.2-6
  • every version on: no fix on record
—
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
org.apache.shiro:shiro-core3.0.0-alpha-1
  • every version up to 2.2.1: fixed in 2.2.1
  • 3.0.0-alpha-0 up to 3.0.0-alpha-2: fixed in 3.0.0-alpha-2
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 22× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 140 total refreshes for this CVE.

  1. 2026-10-09 20:07 UTCEPSS rescore
  2. 2026-10-08 17:12 UTCEPSS rescore
  3. 2026-10-07 23:48 UTCEPSS rescore
  4. 2026-10-06 15:18 UTCEPSS rescore
  5. 2026-10-05 17:43 UTCEPSS rescore
  6. 2026-10-04 23:22 UTCEPSS rescore
  7. 2026-10-03 14:25 UTCEPSS rescore
  8. 2026-10-01 19:50 UTCEPSS rescore
  9. 2026-09-30 15:03 UTCEPSS rescore
  10. 2026-09-28 13:51 UTCEPSS rescore
  11. 2026-09-27 13:48 UTCEPSS rescore
  12. 2026-09-26 15:59 UTCEPSS rescore
  13. 2026-09-26 00:27 UTCEPSS rescore
  14. 2026-09-23 17:53 UTCEPSS rescore
  15. 2026-09-20 20:16 UTCEPSS rescore
  16. 2026-09-18 19:28 UTCEPSS rescore
  17. 2026-09-16 14:08 UTCEPSS rescore
  18. 2026-09-16 05:15 UTCEPSS rescore
  19. 2026-09-14 02:29 UTCEG score recompute
  20. 2026-09-13 16:47 UTCEPSS rescore
  21. 2026-09-13 14:28 UTCEG score recompute
  22. 2026-09-11 14:53 UTCEPSS rescore
  23. 2026-09-10 09:35 UTCEPSS rescore
  24. 2026-09-08 22:01 UTCEPSS rescore
  25. 2026-09-07 16:01 UTCEPSS rescore
Show 75 more
  1. 2026-09-06 13:47 UTCEPSS rescore
  2. 2026-09-04 05:06 UTCEPSS rescore
  3. 2026-09-02 14:12 UTCEPSS rescore
  4. 2026-09-01 13:54 UTCEPSS rescore
  5. 2026-09-01 04:40 UTCEPSS rescore
  6. 2026-08-30 22:24 UTCEG score recompute
  7. 2026-08-30 19:17 UTCEPSS rescore
  8. 2026-08-30 01:22 UTCEPSS rescore
  9. 2026-08-28 21:41 UTCEPSS rescore
  10. 2026-08-27 14:25 UTCEPSS rescore
  11. 2026-08-26 14:46 UTCEPSS rescore
  12. 2026-08-25 13:49 UTCEPSS rescore
  13. 2026-08-24 22:25 UTCEG score recompute
  14. 2026-08-23 04:25 UTCEG score recompute
  15. 2026-08-23 00:19 UTCEPSS rescore
  16. 2026-08-21 23:49 UTCEPSS rescore
  17. 2026-08-21 01:21 UTCEG score recompute
  18. 2026-08-20 22:55 UTCEPSS rescore
  19. 2026-08-20 08:14 UTCEG score recompute
  20. 2026-08-19 17:04 UTCEPSS rescore
  21. 2026-08-19 08:11 UTCEG score recompute
  22. 2026-08-18 13:48 UTCEPSS rescore
  23. 2026-08-17 14:32 UTCEG score recompute
  24. 2026-08-17 13:47 UTCEPSS rescore
  25. 2026-08-16 21:03 UTCEG score recompute
  26. 2026-08-16 14:56 UTCEPSS rescore
  27. 2026-08-16 02:21 UTCEG score recompute
  28. 2026-08-16 02:14 UTCEPSS rescore
  29. 2026-08-15 04:28 UTCEG score recompute
  30. 2026-08-15 01:30 UTCEPSS rescore
  31. 2026-08-13 23:17 UTCEG score recompute
  32. 2026-08-13 22:00 UTCEPSS rescore
  33. 2026-08-12 16:43 UTCEG score recompute
  34. 2026-08-12 13:51 UTCEPSS rescore
  35. 2026-08-11 15:45 UTCEG score recompute
  36. 2026-08-11 03:18 UTCEG score recompute
  37. 2026-08-11 00:00 UTCEPSS rescore
  38. 2026-08-09 13:50 UTCEG score recompute
  39. 2026-08-09 13:46 UTCEPSS rescore
  40. 2026-08-08 17:03 UTCEG score recompute
  41. 2026-08-08 16:37 UTCEPSS rescore
  42. 2026-08-07 20:17 UTCEG score recompute
  43. 2026-08-06 15:08 UTCEG score recompute
  44. 2026-08-06 13:47 UTCEPSS rescore
  45. 2026-08-05 22:30 UTCEG score recompute
  46. 2026-08-05 19:17 UTCEPSS rescore
  47. 2026-08-04 15:26 UTCEG score recompute
  48. 2026-08-04 15:10 UTCEPSS rescore
  49. 2026-08-04 10:39 UTCEPSS rescore
  50. 2026-08-03 14:26 UTCEG score recompute
  51. 2026-08-03 10:36 UTCEPSS rescore
  52. 2026-08-02 06:31 UTCEG score recompute
  53. 2026-08-02 02:27 UTCEPSS rescore
  54. 2026-08-01 05:23 UTCEG score recompute
  55. 2026-08-01 04:16 UTCEPSS rescore
  56. 2026-07-30 22:40 UTCEG score recompute
  57. 2026-07-30 16:28 UTCEPSS rescore
  58. 2026-07-30 03:41 UTCEG score recompute
  59. 2026-07-30 01:30 UTCEPSS rescore
  60. 2026-07-29 02:11 UTCEG score recompute
  61. 2026-07-28 15:37 UTCEPSS rescore
  62. 2026-07-27 18:09 UTCEG score recompute
  63. 2026-07-26 19:09 UTCEG score recompute
  64. 2026-07-26 14:54 UTCEPSS rescore
  65. 2026-07-25 14:18 UTCEPSS rescore
  66. 2026-07-24 14:18 UTCEPSS rescore
  67. 2026-07-23 14:18 UTCEPSS rescore
  68. 2026-07-23 03:18 UTCEG score recompute
  69. 2026-07-22 14:08 UTCEPSS rescore
  70. 2026-07-21 15:25 UTCEPSS rescore
  71. 2026-07-20 17:08 UTCEPSS rescore
  72. 2026-07-19 14:31 UTCEPSS rescore
  73. 2026-07-19 14:31 UTCEPSS rescore
  74. 2026-07-19 02:29 UTCEPSS rescore
  75. 2026-07-18 10:04 UTCEPSS rescore

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCsassoftware/shiro
    First seen Aug 31, 2026

    CVE-2026-49268 — Analysis and Remediation of an LDAP Injection Authentication Bypass Vulnerability

    Open source ↗

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-49268?
CVE-2026-49268 is a critical vulnerability published on June 17, 2026. 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…
When was CVE-2026-49268 disclosed?
CVE-2026-49268 was first published on June 17, 2026, with the most recent update on June 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-49268 actively exploited?
CVE-2026-49268 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (53rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-49268?
CVE-2026-49268 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-49268?
A fix for CVE-2026-49268 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-49268 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-49268

Explore →

Is Your Infrastructure Affected by CVE-2026-49268?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs