CVE-2026-56091

HIGHPre-NVD 8.28.2—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7%, top 49% 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, secondary
8.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 8.2Exploit: None knownExposed services: Not assessed

The CVE record names the fixed release — apply it.

When using Apache Shiro with the shiro-guice module in a web servlet context, a specially crafted HTTP request may cause an authentication bypass. This vulnerability is similar to https://www.cve.org/CVERecord?id=CVE-2020-1957 https://www.cve.org/CVERecord , except that it affects the shiro-guice module instead of the shiro-spring module.

This issue affects all Apache Shiro versions through 2.x, and 3.0.0-alpha-1 only when using shiro-guice module in a web servlet context.

Upgrade to version 3.0.0 or later, which fixes the issue.

CVSS v3
8.2
EG Score
8.2HIGHmedium confidence
EG Risk
42
EG Risk 42/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
Severity82% × 45%
Exploitation1% × 40%
Automatability30% × 15%
EPSS PROB
0.7%
EPSS %ILE
50th
KEV
Not listed

Published

June 25, 2026

Last Modified

June 25, 2026

Advisory Details (1)

Auto-updated Jun 26, 2026
Fix named in the CVE record.
generic
https://lists.apache.org/thread/onmtxmy2qonbpx7xlw3o34x8sctv47r7

Vendor Advisories for CVE-2026-56091(1)

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

Affected Packages

(4 across 4 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
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 34× 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 244 total refreshes for this CVE.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-56091?
CVE-2026-56091 is a high vulnerability published on June 25, 2026. When using Apache Shiro with the shiro-guice module in a web servlet context, a specially crafted HTTP request may cause an authentication bypass. This vulnerability is similar to https://www.cve.org/CVERecord?id=CVE-2020-1957 https://www.cve.org/CVERecord , except that it affects the shiro-guice…
When was CVE-2026-56091 disclosed?
CVE-2026-56091 was first published on June 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-56091 actively exploited?
CVE-2026-56091 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (50th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-56091?
CVE-2026-56091 has a CVSS base score of 8.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-56091?
The CVE record for CVE-2026-56091 names the fix: "Upgrade to version 3.0.0 or later, which fixes the issue." The vendor advisories EchelonGraph has for CVE-2026-56091 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-56091

Explore →

Is Your Infrastructure Affected by CVE-2026-56091?

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

Book a Demo →Browse All CVEs