Apache Shiro before 1.2.5, when a cipher key has not been configured for the "remember me" feature, allows remote attackers to execute arbitrary code or bypass intended access restrictions via an unspecified request parameter.
CVE-2016-4437
Score elevated to 9.8 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2021-11-03), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 9.8 retained for reference. Confidence: HIGH.
- Actively exploited in the wild (CISA-KEV)
A fix is available — apply it.
- CVSS v3
- 9.8
- EG Score
- 9.8(high)
- EG Risk
- 99(Act)EG Risk 99/100SSVC: Act
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 computedSeverity98% × 45%Exploitation100% × 40%Automatability100% × 15%Action: Fix now — active exploitation, automatable, high impact. - EPSS
- 99.8%
- KEV
- ⚠ Exploited
Published
June 7, 2016
Last Modified
April 22, 2026
Advisory Details (5)
Auto-updated May 12, 2026Patch Availability(3)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| ubuntu | libshiro-java (1.2.4-1ubuntu0.1~esm1) @ xenial | 2026-07-22 | ubuntu |
| redhat | patch | 2016-10-06 | redhat |
| redhat | patch | 2016-10-06 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(1 across 1 ecosystem)
Maven(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| org.apache.shiro:shiro-core | 1.0.0-incubating ... 1.2.4 (7 versions) | 1.2.5 | — |
All Vendor Advisories
(3)
Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.
Data Freshness Timeline
(refreshed 47× in last 7d / 194× 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 364 total refreshes for this CVE.
- 2026-07-23 01:23 UTCEG score recompute
- 2026-07-22 22:50 UTCVendor advisory
- 2026-07-22 22:02 UTCEG score recompute
- 2026-07-22 19:40 UTCCISA KEV update
- 2026-07-22 18:28 UTCVendor advisory
- 2026-07-22 14:08 UTCVendor advisory
- 2026-07-22 09:47 UTCVendor advisory
- 2026-07-22 05:26 UTCVendor advisory
- 2026-07-22 01:05 UTCVendor advisory
- 2026-07-21 18:36 UTCVendor advisory
- 2026-07-21 14:37 UTCCISA KEV update
- 2026-07-21 14:15 UTCVendor advisory
- 2026-07-21 09:54 UTCVendor advisory
- 2026-07-21 05:34 UTCVendor advisory
- 2026-07-21 01:13 UTCVendor advisory
- 2026-07-20 20:53 UTCVendor advisory
- 2026-07-20 16:32 UTCVendor advisory
- 2026-07-20 12:10 UTCVendor advisory
- 2026-07-20 07:49 UTCVendor advisory
- 2026-07-20 03:29 UTCVendor advisory
- 2026-07-19 23:09 UTCVendor advisory
- 2026-07-19 18:49 UTCVendor advisory
- 2026-07-19 14:29 UTCVendor advisory
- 2026-07-19 10:09 UTCVendor advisory
- 2026-07-19 05:49 UTCEG score recompute
Show 75 moreShow fewer
- 2026-07-19 05:49 UTCVendor advisory
- 2026-07-19 02:26 UTCEPSS rescore
- 2026-07-19 02:26 UTCEPSS rescore
- 2026-07-19 01:29 UTCVendor advisory
- 2026-07-18 21:08 UTCVendor advisory
- 2026-07-18 16:48 UTCVendor advisory
- 2026-07-18 12:28 UTCVendor advisory
- 2026-07-18 08:08 UTCVendor advisory
- 2026-07-18 03:48 UTCVendor advisory
- 2026-07-17 23:28 UTCVendor advisory
- 2026-07-17 19:08 UTCVendor advisory
- 2026-07-17 14:48 UTCVendor advisory
- 2026-07-17 10:27 UTCEG score recompute
- 2026-07-17 10:27 UTCVendor advisory
- 2026-07-17 06:06 UTCVendor advisory
- 2026-07-17 01:45 UTCVendor advisory
- 2026-07-16 21:25 UTCVendor advisory
- 2026-07-16 17:04 UTCVendor advisory
- 2026-07-16 17:04 UTCCISA KEV update
- 2026-07-16 12:43 UTCVendor advisory
- 2026-07-16 08:20 UTCVendor advisory
- 2026-07-16 04:00 UTCVendor advisory
- 2026-07-15 23:40 UTCVendor advisory
- 2026-07-15 19:20 UTCVendor advisory
- 2026-07-15 16:54 UTCEPSS rescore
- 2026-07-15 16:54 UTCEPSS rescore
- 2026-07-15 16:49 UTCCISA KEV update
- 2026-07-15 15:04 UTCCISA KEV update
- 2026-07-15 15:00 UTCVendor advisory
- 2026-07-15 10:39 UTCVendor advisory
- 2026-07-15 06:18 UTCVendor advisory
- 2026-07-15 01:58 UTCVendor advisory
- 2026-07-14 21:38 UTCVendor advisory
- 2026-07-14 18:05 UTCCISA KEV update
- 2026-07-14 17:17 UTCVendor advisory
- 2026-07-14 12:53 UTCVendor advisory
- 2026-07-14 08:33 UTCVendor advisory
- 2026-07-14 04:13 UTCVendor advisory
- 2026-07-13 23:53 UTCVendor advisory
- 2026-07-13 19:32 UTCVendor advisory
- 2026-07-13 17:07 UTCCISA KEV update
- 2026-07-13 15:10 UTCVendor advisory
- 2026-07-13 10:50 UTCVendor advisory
- 2026-07-13 06:29 UTCVendor advisory
- 2026-07-13 02:08 UTCVendor advisory
- 2026-07-12 21:48 UTCVendor advisory
- 2026-07-12 17:28 UTCVendor advisory
- 2026-07-12 13:08 UTCVendor advisory
- 2026-07-12 08:48 UTCVendor advisory
- 2026-07-12 05:43 UTCEPSS rescore
- 2026-07-12 05:43 UTCEPSS rescore
- 2026-07-12 04:28 UTCVendor advisory
- 2026-07-12 00:06 UTCVendor advisory
- 2026-07-11 19:46 UTCVendor advisory
- 2026-07-11 15:26 UTCVendor advisory
- 2026-07-11 11:06 UTCVendor advisory
- 2026-07-11 06:45 UTCVendor advisory
- 2026-07-11 02:25 UTCVendor advisory
- 2026-07-10 22:05 UTCVendor advisory
- 2026-07-10 17:52 UTCCISA KEV update
- 2026-07-10 17:45 UTCVendor advisory
- 2026-07-10 13:25 UTCVendor advisory
- 2026-07-10 09:05 UTCVendor advisory
- 2026-07-10 04:42 UTCVendor advisory
- 2026-07-10 00:21 UTCVendor advisory
- 2026-07-09 20:00 UTCVendor advisory
- 2026-07-09 15:39 UTCVendor advisory
- 2026-07-09 11:17 UTCVendor advisory
- 2026-07-09 06:57 UTCVendor advisory
- 2026-07-09 02:37 UTCVendor advisory
- 2026-07-08 22:17 UTCVendor advisory
- 2026-07-08 17:57 UTCVendor advisory
- 2026-07-08 13:37 UTCVendor advisory
- 2026-07-08 09:15 UTCVendor advisory
- 2026-07-08 04:55 UTCVendor advisory
Publicly available exploits
(6 references)Working exploit code is in the public domain (1 Metasploit module) (3 GitHub PoCs) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
- GitHub PoCpizza-power/CVE-2016-4437First seen Dec 22, 2023
Python POC to Exploit CVE-2016-4437 Apache Shiro Deserialization Vulnerability Due to Hardcode Encryption Key
Open source ↗ - GitHub PoC4nth0ny1130/shisoserialFirst seen Dec 23, 2021
一个针对shiro反序列化漏洞(CVE-2016-4437)的快速利用工具/A simple tool targeted at shiro framework attacks with ysoserial.
Open source ↗ - GitHub PoCbkfish/Awesome_shiroFirst seen May 27, 2020
CVE-2016-4437-Shiro反序列化爆破模块和key,命令执行,反弹shell的脚本
Open source ↗ - Exploit-DBEDB-48410✓ verifiedFirst seen May 1, 2020
Apache Shiro 1.2.4 - Cookie RememberME Deserial RCE (Metasploit)
Open source ↗ - Metasploitexploit/multi/http/shiro_rememberme_v124_deserialize✓ verifiedFirst seen Jun 7, 2016
Apache Shiro v1.2.4 Cookie RememberME Deserial RCE
Open source ↗ - Nucleihttp/cves/2016/CVE-2016-4437.yamlFirst seen Jan 1, 2016
Apache Shiro 1.2.4 Cookie RememberME - Deserial Remote Code Execution Vulnerability
Open source ↗
Related CVEs(same vendor)
Frequently asked(6)
What is CVE-2016-4437?
When was CVE-2016-4437 disclosed?
Is CVE-2016-4437 actively exploited?
What is the CVSS score of CVE-2016-4437?
Which products are affected by CVE-2016-4437?
How do I remediate CVE-2016-4437?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2016-4437
Is Your Infrastructure Affected by CVE-2016-4437?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.