Auto-added after CISA flagged Shiro as actively exploited (KEV catalog). Version and lifecycle mapping is pending review, so this is assessed at the product level and is never reported as a confident "healthy".
Summary iPlain-English security verdict for Shiro, generated from its current health score, actively-exploited vulnerabilities, and latest supported version.
Shiro currently scores 67/100 — needs attention. No tracked vulnerabilities are currently known to be exploited in the wild. Patch the open issues below when you can.
Disclosure trend iNew CVEs published for Shiro each year (NVD). A higher bar means more disclosures that year — more scrutiny, not necessarily less safe.
Patch priority — what to act on iThe issues to fix first — actively exploited (CISA KEV) first, then by exploitation probability (EPSS), then severity. Each row's "→ fixed in" is the earliest version that patches it; "see advisory" means no fixed version is published.
Most urgent first — actively exploited, then likeliest to be exploited.
CVE-2026-49268 CRITICAL CWE-90 EPSS 1% → fixed in 2.2.1Get alerted about Shiro
Be emailed the moment Shiro gets a newly exploited vulnerability (CISA KEV) or a release reaches end of life. Free · double opt-in · unsubscribe anytime.
We email only on real events for Shiro — no marketing, no sharing, and we never know what you run. Track your whole stack →
Frequently asked
Is Shiro safe and patched?
Shiro currently scores 67/100 — needs attention. No tracked vulnerabilities are currently known to be exploited in the wild. Patch the open issues below when you can.
What should I do about Shiro now?
Review the patch-priority list, apply the available fixes (or move to the latest release), and confirm against Apache's official advisory.
Why is Shiro listed on IsItPatched?
Shiro was added automatically because CISA's Known Exploited Vulnerabilities (KEV) catalog flagged it as actively exploited in the wild. IsItPatched tracks its known CVEs, severity (CVSS), exploitation probability (EPSS) and KEV status from public data; its version and lifecycle mapping is verified over time.
Has Shiro been actively exploited?
Yes. CISA added Shiro to its Known Exploited Vulnerabilities (KEV) catalog after confirming exploitation in the wild — the triggering vulnerability is CVE-2016-4437. Make sure you are running a patched, supported version of Shiro and confirm it against Apache's security advisory.
Similar software we track
More from Apache tracked on IsItPatched.
lifecycle unknown — needs latest supported version
Informational only, from public data (NVD · CISA KEV · EPSS · endoflife.date), and can lag or miss vendor-specific fixes. Always confirm against Apache's official advisory before you patch or upgrade — Shiro official site ↗