← console
voxell vciy

CVE-2016-1544

ROUTINE

Telemetry drift only. No threshold crossed and no authority ruling changed.

CVE record, CISA KEV and EPSS as of 2026-10-18.

CVEs like this one computed, by meaning

What to do now held facts and links

  1. Upgrade to nghttp2 1.7.1 or later upper bounds of the CVE record's affected ranges
  2. Record your decision, dated and frozen with today's evidence: patch by a date · mitigated by a compensating control · deferred · accepted the risk · not affected
  3. Check your version against the ranges this record publishes.

What it is stated by the CNA

nghttp2 before 1.7.1 allows remote attackers to cause a denial of service (memory exhaustion).

weakness
Other
affected
nghttp2
published ranges
nghttp2 < 1.7.1; fedoraproject fedora 22; fedoraproject fedora 23
first unaffected version, by branch
nghttp2 1.7.1
assigned by
certcc
published
2020-02-06

check us bugzilla.redhat.com github.com github.com security.gentoo.org

Exploit code held, dated

exploit code
None held in the PoC-in-GitHub feed. A public repository changes this brief.

What moved held, dated

dateEPSSevent
4 Feb 20220.01232
7 Mar 20230.00098scoring model v2023.03.01
8 Mar 20230.00098
17 Dec 20240.00075
17 Mar 20250.0088scoring model v2025.03.14
1 Mar 20260.00699
4 Mar 20260.01589
23 Apr 20260.01039
15 Jun 20260.00886scoring model v2026.06.15

48 observations held. A step marked with a scoring model moved because the measurement was replaced, not because the vulnerability changed.

Outside the record researched, cited

This section reads the record's references and adds cited findings from outside it. It needs an account. Everything above is held facts and is complete without it.

Sign in to add the researched section

What would change this brief held, dated

CISA KEV
Not listed in the catalogue we hold. A listing changes this brief.
exploit probability
0.01 on 2026-06-15 (FIRST's EPSS, a probability and not evidence of exploitation). Next band line: 10% (0.10). Crossing a line changes this brief.
fix
Held: nghttp2 1.7.1. A newer fix from the CNA or OSV changes this brief.

Watch this CVE What counts as a move

How to check this

Every value above is held with two dates: when it was true upstream (as_of) and when we recorded it (tx_from). Re-derive the exploit probability as it stood on any date:

SELECT value, source, source_version, as_of, tx_from
FROM volatile_valid_as_of('CVE-2016-1544', '2026-10-30T23:59:59.999999Z', now());