vciy

CVE-2016-4437

INDEX BUILT · 2026-09-20

No source can show you its own past. This one can.

Print this page to keep the view as it stands on this date. Everything hidden behind a disclosure opens, and every receipt prints with its value.

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…

CVE-2016-44373 of 4 sources documented this
76

rank 76 = 40 + 25 + 0 + 5 + 6

rank@v1 · act now

Someone is already using it

CISA KEV catalog · public proof-of-concept · FIRST EPSS

EPSS 0.93039 · CISA KEV listed  ·  without this subject the record ranks 36

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 9.8, from NVD  ·  without this subject the record ranks 51

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

no persisting rise in 365 days  ·  without this subject the record ranks 76

How much of the world it touches

NVD CPE configurations

4 products in the CPE ranges  ·  without this subject the record ranks 71

Someone else already set the date

CISA KEV remediation due date

CISA remediation date held  ·  without this subject the record ranks 70

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$4.64Mover the next 30 days, if this record is yours
Movementno material movementthe record holds only daily drift and scoring model releases
Basisassumeda published average, not your estate

$4.64M = $4.99M incident cost x 1 exposure x 0.93039 likelihood

udv@v1 · unaudited · wrong for you until you say what you run

$4.99M is the cost of a breach that happened, from IBM Cost of a Data Breach Report 2026, global average. It is not the value of any asset of yours. That average already covers breaches of every severity, so scaling it by exposure understates a partial-impact record. That is an assumption, not a measurement. Your own asset value goes in the decision record.

Hindsight · the state

0.93039EPSSKEV · LISTED
Severity9.8 CRITICALreceipt
Harmtotal loss · unauthenticatedreceipt
Exploitationin the wild · KEVreceipt
Defenseunaffected versions publishedreceipt
Movementsteadyreceipt
PLATEAU10Minimal movement since 2022-02-04, 1673 days at 0.93, as of 2026-09-04. arc-rules@v1

Foresight · where to check next

No weakness class or product neighbourhood is held for this record, so this index cannot name anywhere to check next. That is an absence in the record, not a finding about the software.

Color is a claim, not decoration:the hostile worldthe defenseno signal

Check a version against this record

A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.

Watch this record

Matches your own product list against every record this index holds, and tells you when one of them moves.

What counts as a move

Set up a watchlist (needs a Practitioner account)

Record your call

Keep your verdict, your reason and the evidence together. The record takes its date when you save it.

AcceptDeferPatch by…Not affectedMitigated

Choose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.

Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.

Harm, if it fires from the vector and the weakness

Written for the ticket you're about to file.

Reachnetwork-reachable · no privileges required · no user interaction · low attack complexityreceipt
ImpactComplete confidentiality, integrity and availability lossreceipt
Scored fromCVSS v3.1 · NVD's vectorreceipt
Weakness classCWE-321 Use of Hard-coded Cryptographic Keyreceipt
Published consequencesCWE-321: Access Control: Bypass Protection Mechanism, Gain Privileges or Assume Identity, Read Application Data[email protected]
Ransomware campaign useUnknown to CISAreceipt

CISA KEV & Federal Remediation Deadline from the record and CISA

The fix, and how long it's been waiting.

First unaffected version, by branchshiro 1.2.5; aurora 0.18.1receipt
Patch available sinceNo dated patch-availability record in held sources. The index holds reference URLs without dates and only the current revision of the CVE record, so the day a fix first existed cannot be derived. Only the versions it landed in.
CISA remediation statusoverdue since 2022-05-03receipt
CISA required actionApply updates per vendor instructions.receipt
Published to CISA KEV1975 daysderived

Exploit Status & Known PoCs a ladder, not a score

Current rung: Exploited in the wild · CISA KEV listed, 2021-11-03.

  • RUNG 1Nothing observed in held sources
  • RUNG 2Proof-of-concept published · 6 public repositories2020-05-27receipt
  • RUNG 3Exploited in the wild · CISA KEV listed2021-11-03receipt
  • RUNG 4Ransomware campaign use known

Authority who says so

CVSS, NVD9.8 CRITICALreceipt
Exploit probability0.93039 · top 0.17% of all CVEsreceipt
Blast breadth4 products across 2 vendorsderived
Assigned byredhatreceipt
Recorded changes46 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Named in the CPE rangesApache shiro; Apache aurora; Redhat fuse; and 1 morereceipt
Published rangesapache aurora >= 0.10.0 < 0.18.1; apache shiro < 1.2.5; redhat fuse 1.0; redhat jboss middleware text-only advisories 1.0receipt

A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.

Did this affect your environment?Answering needs an account.

What it is stated by the CNA

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. receipt

NVD's analysis a second authority

severity
9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
weakness
CWE-321
affected versions
apache aurora >= 0.10.0 < 0.18.1; apache shiro < 1.2.5; redhat fuse 1.0; and 1 more, listed in full below
also scored by
9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

check it yourself rhn.redhat.com lists.apache.org packetstormsecurity.com rhn.redhat.com securityfocus.com securityfocus.com +1 morereceipt

Dated events

2021-11-03Added to CISA KEV2022-05-03CISA remediation due

Movement the material steps

4 Feb 20220.9454
7 Mar 20230.9748 · scoring model v2023.03.01
17 Mar 20250.94344 · scoring model v2025.03.14
15 Jun 20260.93143 · scoring model v2026.06.15
18 Jul 20260.93039
Show all 32 observations
4 Feb 20220.9454
7 Mar 20230.9748
8 Mar 20230.97480
11 May 20230.97499
26 May 20230.97483
31 Jul 20230.97507
24 Jan 20240.97496
26 Feb 20240.97481
30 Mar 20240.97488
1 May 20240.97490
7 Jul 20240.97494
25 Jul 20240.97135
20 Nov 20240.97050
17 Dec 20240.97171
31 Dec 20240.97204
12 Feb 20250.97233
17 Mar 20250.94344
4 May 20250.94303
1 Jan 20260.94252
4 Jan 20260.94303
14 Jan 20260.94214
1 Feb 20260.94092
4 Feb 20260.94214
1 Mar 20260.94092
4 Mar 20260.94214
21 Mar 20260.94251
15 Apr 20260.94214
22 May 20260.94284
27 May 20260.94251
15 Jun 20260.93143
11 Jul 20260.92988
18 Jul 20260.93039

32 observations held. A highlighted step crossed a promotion threshold. A step marked with a scoring model moved because the instrument was replaced, not because the vulnerability changed. receipt

The full biography

EPSS 0.93039Published2016-06-07Public PoC2020-05-27CISA KEV2021-11-03Index as of2026-09-04

Listed by CISA 1975 days after it published and the record had been public for 10 years, 2 months when this index was last written.

No material movement in 48 days as of the last ingest this index recorded.

Published 2016-06-07 receipt · Public PoC 2020-05-27 receipt · CISA KEV 2021-11-03 receipt · Index as of 2026-09-04 derived

Siblings and hubs

Records related to this one

Browse the index from here

These are index-wide views, not findings about CVE-2016-4437.

What usually comes next

Everything above needs no account. What is below is work: assembling it, scoping it to your estate, watching it, and handing it to someone else.

Everything on this page is free. Public data. Withholding it protects nothing.