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.4%, top 66% 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
Trending — 3 sources updated this week
8.2
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.2Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.2(medium)
EPSS
34.0%
KEV
Not listed

Published

June 25, 2026

Last Modified

June 25, 2026

Advisory Details (1)

Auto-updated Jun 26, 2026
No patch confirmed yet.
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.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 36× in last 7d / 62× 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.

  1. 2026-07-07 03:58 UTCEG score recompute
  2. 2026-07-07 03:58 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 14:57 UTCEG score recompute
  6. 2026-07-06 14:57 UTCGHSA enrichment
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-06 02:02 UTCEG score recompute
  10. 2026-07-06 02:01 UTCGHSA enrichment
  11. 2026-07-05 13:07 UTCEG score recompute
  12. 2026-07-05 13:07 UTCGHSA enrichment
  13. 2026-07-05 02:31 UTCEPSS rescore
  14. 2026-07-05 02:30 UTCEPSS rescore
  15. 2026-07-05 00:13 UTCEG score recompute
  16. 2026-07-05 00:13 UTCGHSA enrichment
  17. 2026-07-04 11:16 UTCEG score recompute
  18. 2026-07-04 11:16 UTCGHSA enrichment
  19. 2026-07-04 06:31 UTCEPSS rescore
  20. 2026-07-04 06:31 UTCEPSS rescore
  21. 2026-07-03 22:22 UTCEG score recompute
  22. 2026-07-03 22:22 UTCGHSA enrichment
  23. 2026-07-03 09:27 UTCEG score recompute
  24. 2026-07-03 09:27 UTCGHSA enrichment
  25. 2026-07-02 20:34 UTCEG score recompute
Show 37 more
  1. 2026-07-02 20:33 UTCGHSA enrichment
  2. 2026-07-02 07:40 UTCEG score recompute
  3. 2026-07-02 07:39 UTCGHSA enrichment
  4. 2026-07-01 18:46 UTCEG score recompute
  5. 2026-07-01 18:45 UTCGHSA enrichment
  6. 2026-07-01 15:07 UTCEPSS rescore
  7. 2026-07-01 05:52 UTCEG score recompute
  8. 2026-07-01 05:52 UTCGHSA enrichment
  9. 2026-06-30 23:22 UTCEPSS rescore
  10. 2026-06-30 16:58 UTCEG score recompute
  11. 2026-06-30 16:58 UTCGHSA enrichment
  12. 2026-06-30 04:04 UTCEG score recompute
  13. 2026-06-30 04:03 UTCGHSA enrichment
  14. 2026-06-29 15:08 UTCEG score recompute
  15. 2026-06-29 15:08 UTCGHSA enrichment
  16. 2026-06-29 14:06 UTCEPSS rescore
  17. 2026-06-29 14:06 UTCEPSS rescore
  18. 2026-06-29 02:14 UTCEG score recompute
  19. 2026-06-29 02:14 UTCGHSA enrichment
  20. 2026-06-28 14:07 UTCEPSS rescore
  21. 2026-06-28 13:20 UTCEG score recompute
  22. 2026-06-28 13:20 UTCGHSA enrichment
  23. 2026-06-28 04:56 UTCEPSS rescore
  24. 2026-06-28 04:56 UTCEPSS rescore
  25. 2026-06-28 00:26 UTCEG score recompute
  26. 2026-06-28 00:26 UTCGHSA enrichment
  27. 2026-06-27 11:33 UTCEG score recompute
  28. 2026-06-27 11:32 UTCGHSA enrichment
  29. 2026-06-27 03:08 UTCEPSS rescore
  30. 2026-06-26 22:38 UTCEG score recompute
  31. 2026-06-26 22:38 UTCGHSA enrichment
  32. 2026-06-26 09:42 UTCEG score recompute▲ 8.20
  33. 2026-06-26 09:42 UTCGHSA enrichment
  34. 2026-06-26 09:42 UTCNVD updateCVSS v3 → 8.2 · CVSS v4 → 8.2
  35. 2026-06-25 13:49 UTCEPSS rescore
  36. 2026-06-25 10:02 UTCEG score recompute
  37. 2026-06-25 10:02 UTCGHSA enrichment

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 in the National Vulnerability Database 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 34.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-56091?
CVE-2026-56091 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2026-56091?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56091, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for 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.

Start Free Scan →Browse All CVEs