CVE-2016-4437
CVE-2016-4437 is a critical-severity vulnerability (CVSS 3.1 base score 9.8). Apache Shiro contains a vulnerability which may allow remote attackers to execute code or bypass intended access restrictions via an unspecified request parameter when a cipher key has not been configured for the "remember me" feature. CISA added it to the Known Exploited Vulnerabilities catalog on 2021-11-03, with a remediation due date of 2022-05-03 for US federal civilian agencies. As of 2026-11-22, EPSS estimates a 93.0% probability of exploitation in the next 30 days, in the 99th percentile of scored CVEs.
Updated
- CVSS 3.1
- 9.8 CRITICAL
- EPSS
- 93.0% (99th pct)
- CISA KEV
- Exploited
- Published
- 2016-06-07
- Weakness
- CWE-321
Apache Shiro Code Execution Vulnerability is confirmed as actively exploited and is listed in the CISA KEV catalog.
Required action
Apply updates per vendor instructions.
CISA notes
https://nvd.nist.gov/vuln/detail/CVE-2016-4437
Description
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.
Key Findings
as of 2026-11-22- CISA added CVE-2016-4437 to the KEV catalog 1,975 days after its CVE record was published.
- It is one of 43 Apache entries in the CISA KEV catalog, and one of 12 added in 2021.
- Its current EPSS score (93.0%) is higher than that of 75% of CISA KEV entries.
Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HOpen in CVSS calculator Remediation Timeline
BOD 26-04, US federal agenciesDeadlines for US federal civilian agencies under Table 1 of CISA BOD 26-04, from the CVE's KEV status (listed) and CISA's SSVC values (automatable yes, technical impact total, 2025-02-07).
How the timeline is set
Table 1 of CISA's Binding Operational Directive 26-04 sets the time US federal civilian agencies have to remediate a vulnerability. It depends on four inputs: whether the asset is publicly exposed, whether the CVE is in the KEV catalog, whether an adversary can automate its exploitation, and whether exploitation gives partial or total control of the asset, which SSVC calls technical impact. CISA publishes the last three for every CVE through services such as its Vulnrichment program.
Days are calendar days. The clock starts at whichever comes first: CISA adds the CVE to the KEV catalog, or the agency identifies the vulnerability on an asset and reports it to its Continuous Diagnostics and Mitigation (CDM) dashboard. A publicly exposed asset is accessible to unauthenticated or untrusted entities via public networks, such as the internet. Forensic triage means assessing the asset to determine whether it has been compromised.
CISA calculates the KEV due date with the same table, using its own evidence on whether the vulnerability is present in a publicly exposed asset. Each agency makes the final exposure decision for each of its assets.
Affected Products
| Vendor | Product | Affected versions |
|---|---|---|
| - | - | n/a |
References
7 linksVendor advisories
Mailing lists
Vulnerability databases
Other references
Record Details
- Publicly disclosed
- 2016-06-03
- Published
- 2016-06-07
- Last updated
- 2025-10-21
- Assigner (CNA)
- redhat
- Credited to
- -
More from Apache
Apache Log4j2 JNDI features do not protect against attacker controlled LDAP and other JNDI related endpoints
Apache Struts Remote Code Execution Vulnerability
mod_proxy SSRF
Apache Struts Improper Input Validation Vulnerability
CVE record data © The MITRE Corporation, used under the CVE Terms of Use. Exploited-in-the-wild data from the CISA Known Exploited Vulnerabilities catalog (CC0). Exploit prediction scores by FIRST EPSS (first.org/epss). Alert titles and links from CISA cybersecurity alerts. This site is not affiliated with or endorsed by MITRE, NVD, CISA, or FIRST.