CVE-2016-4437 — Apache Shiro Code Execution Vulnerability
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- Confirmed exploitation (CISA KEV)+35
- Public exploit/PoC (nuclei, metasploit, exploitdb)+20
- EPSS 93% (30-day exploitation probability)+15
- Technical severity (critical)+10
- Automatable exploitation (SSVC)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Maven Org.apache.shiro:shiro-core: fixed in version 1.2.5 — github.com (GitHub Security Advisories)
CISA required action CISA
Apply updates per vendor instructions.
US federal deadline: May 3, 2022 — passed 1626 day(s) ago
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Apache Software Foundation Aurora, Apache Software Foundation Shiro, Red Hat Fuse…).
- Treat as emergency remediation: the CVE is in CISA KEV (confirmed exploitation).
- The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
- Apply the fixed version or the patch documented under Remediation.
- EPSS ahead of 100% of scored CVEs: prioritize it in the patch queue.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Apache Software Foundation | Aurora | ≥ 0.10.0 and < 0.18.1 | Vulnerable | NIST National Vulnerability Database |
| Apache Software Foundation | Shiro | < 1.2.5 | Vulnerable | NIST National Vulnerability Database |
| Red Hat | Fuse | version 1.0 | Vulnerable | NIST National Vulnerability Database |
| Red Hat | Jboss Middleware Text-only Advisories | version 1.0 | Vulnerable | NIST National Vulnerability Database |
| Maven | Org.apache.shiro:shiro-core | ≤ 1.2.4 | Vulnerable | GitHub Security Advisories |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 9.8 | CVSS 3.1 | Critical | 3.9 | 5.9 | nvd@nist.gov via NIST National Vulnerability Database |
| 9.8 | CVSS 3.1 | Critical | 3.9 | 5.9 | 134c704f-9b21-4f2e-91b3-4a467353bcc0 via NIST National Vulnerability Database |
| 9.8 | CVSS 3.1 | Critical | — | — | GitHub, Inc. via GitHub Security Advisories |
| 9.8 | CVSS 3.1 | Critical | — | — | CISA-ADP via CVE Program (cve.org) e CISA ADP |
| 6.8 | CVSS 2.0 | Medium | 8.6 | 6.4 | nvd@nist.gov via NIST National Vulnerability Database |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (score shown at the top: nvd@nist.gov) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
CISA KEV details CISA
CISA lists a CVE once it has evidence of exploitation against real targets.
CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a reference date.
Public exploits, PoCs and detection templates
Public code that demonstrates or tests the flaw raises the odds of mass exploitation — and Nuclei templates help find vulnerable assets in your environment.
- Apache Shiro v1.2.4 Cookie RememberME Deserial RCE excellent Jun 7, 2016
- Apache Shiro 1.2.4 - Cookie RememberME Deserial RCE (Metasploit) verified May 1, 2020
Warning: public PoCs are sometimes disguised malware. Use them only for authorized testing in an isolated environment. This portal does not host exploit code — it only points to the sources.
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 93.04%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Hunt retroactively in logs from before Nov 3, 2021 (KEV listing): exploitation may have started earlier.
Timeline
What happened to this CVE, newest first.
- 2026
- Fix documented
- Affected products added · maven/org.apache.shiro:shiro-core
- Affected products added · apache/aurora, apache/shiro, redhat/fuse, redhat/jboss middleware text-only advisories
- Source status changed · Published → Analyzed
- Record published
- CVSS changed · 9.8
- Source status changed · → Published
- SSVC assessment updated
- Added to CISA KEV (detected)
- Record created in this database
- 2021
- Added to CISA KEV catalog
- 2016
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 3× References added · Oct 13, 2026 – Oct 13, 2026
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
11 on the record
- www.cisa.gov/known-exploited-vulnerabilities-catalog
- lists.apache.org/thread.html/ef3a800c7d727a00e04b78e2f06c5cd8960f09ca28c9b69d94c3c4c4%
- rhn.redhat.com/errata/RHSA-2016-2036.html
- github.com/advisories/GHSA-p836-389h-j692
- www.securityfocus.com/archive/1/538570/100/0/threaded
- packetstormsecurity.com/files/137310/Apache-Shiro-1.2.4-Information-Disclosure.html
- lists.apache.org/thread.html/ef3a800c7d727a00e04b78e2f06c5cd8960f09ca28c9b69d94c3c4c4@
- www.securityfocus.com/bid/91024
- packetstormsecurity.com/files/157497/Apache-Shiro-1.2.4-Remote-Code-Execution.html
- nvd.nist.gov/vuln/detail/CVE-2016-4437
- rhn.redhat.com/errata/RHSA-2016-2035.html
Elsewhere on this site
Related CVEs (same products)
- Low CVE-2026-56130 Apache Shiro: Remember-me cookie isn't checked for expiry on the server Jun 25, 2026
- High CVE-2026-56091 Apache Shiro: Authentication bypass in Guice-Web integration Jun 25, 2026
- Critical CVE-2026-49268 Apache Shiro: LDAP DN Injection in DefaultLdapRealm Jun 17, 2026
- High CVE-2026-41731 In Spring for Apache Kafka, overly broad trusted-package matching in header mappers exposes JDK classes to deserialization Jun 9, 2026
- Medium CVE-2026-48589 Apache Shiro: Jakarta EE open redirect via untrusted Referer in post-login redirect flow May 25, 2026
- Medium CVE-2026-44598 Apache Shiro Jakarta EE module: Open redirect and SSRF (requires valid credentials) May 25, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2016-4437 is "Apache Shiro Code Execution Vulnerability", rated Critical. It affects Aurora (Apache Software Foundation); versions are in the scope table. It is in CISA KEV: there is evidence of real-world exploitation. CVSS 9.8 describes technical severity. EPSS 93.04% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.