CVE-2026-106972

HIGHPre-NVD 7.57.5
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-10-28. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS, GitHub Security Advisory
Elevated

Also known asEUVD-2026-112133 (ENISA EUVD) · GHSA-hw75-hpgq-ph8x (GitHub Security Advisories)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 7.5Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Uncontrolled recursion in MessagePack\BufferUnpacker::unpack() in rybakit/msgpack versions prior to 0.11.0 allows attackers to cause a denial of service through memory exhaustion when an application decodes deeply nested, attacker-controlled MessagePack input.

CVSS v3
7.5
EG Score
7.5HIGHhigh confidence
EG Risk
65
EG Risk 65/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.3%
EPSS %ILE
27th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 28, 2026

Last Modified

October 30, 2026

Advisory Details (3)

Auto-updated Oct 30, 2026
🔬 Proof of concept available. Patch available. Sources: github_release.
Web page🟡 PoC Available

security-advisories/CVE-2026-106972.md at main · diptendukar/security-advisories · GitHub

https://github.com/diptendukar/security-advisories/blob/main/CVE-2026-106972.md
GitHub release Patch Available

v0.11.0

Patch available: rybakit/msgpack.php v0.11.0

https://github.com/rybakit/msgpack.php/releases/tag/v0.11.0
Web page

GitHub - rybakit/msgpack.php: A pure PHP implementation of the MessagePack serialization format / msgpack.org[PHP] · GitHub

https://github.com/rybakit/msgpack.php

Vendor Advisories for CVE-2026-106972(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 27× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-12 18:53 UTCEchelonGraph re-scored
  2. 2026-11-12 18:53 UTCGHSA enrichmentGHSA-hw75-hpgq-ph8x · GitHub severity HIGH · GitHub CVSS 7.5
  3. 2026-11-12 16:32 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  4. 2026-11-11 16:37 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  5. 2026-11-10 16:41 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  6. 2026-11-09 16:34 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  7. 2026-11-08 16:38 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  8. 2026-11-07 16:38 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  9. 2026-11-06 16:35 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  10. 2026-11-06 06:37 UTCEchelonGraph re-scored
  11. 2026-11-06 06:37 UTCGHSA enrichmentGHSA-hw75-hpgq-ph8x · GitHub severity HIGH · GitHub CVSS 7.5
  12. 2026-11-04 16:34 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  13. 2026-11-03 16:46 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  14. 2026-11-02 16:43 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  15. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  16. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  17. 2026-10-30 18:26 UTCGHSA enrichmentGHSA-hw75-hpgq-ph8x
  18. 2026-10-30 17:27 UTCEchelonGraph re-scored
  19. 2026-10-30 17:27 UTCGHSA enrichmentGHSA-hw75-hpgq-ph8x
  20. 2026-10-30 17:21 UTCEchelonGraph re-scoredFirst assessed: 7.5 HIGH
  21. 2026-10-30 17:21 UTCGHSA enrichmentGHSA-hw75-hpgq-ph8x
  22. 2026-10-30 17:20 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
  23. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  24. 2026-10-29 17:28 UTCGHSA enrichmentGHSA-hw75-hpgq-ph8x
  25. 2026-10-29 17:26 UTCNVD update
Show 8 more
  1. 2026-10-29 17:17 UTCEchelonGraph re-scored
  2. 2026-10-29 17:17 UTCGHSA enrichmentGHSA-hw75-hpgq-ph8x
  3. 2026-10-29 17:16 UTCMITRE cvelistV5
  4. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  5. 2026-10-28 15:26 UTCNVD update
  6. 2026-10-28 15:01 UTCENISA EUVD ID recordedEUVD-2026-112133 · Source: ENISA EUVD
  7. 2026-10-28 14:27 UTCEchelonGraph re-scored
  8. 2026-10-28 14:24 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-106972?
CVE-2026-106972 is a high-severity vulnerability; its CVE record was published on October 28, 2026. Uncontrolled recursion in MessagePack\BufferUnpacker::unpack() in rybakit/msgpack versions prior to 0.11.0 allows attackers to cause a denial of service through memory exhaustion when an application decodes deeply nested, attacker-controlled MessagePack input.
When was the CVE record for CVE-2026-106972 published?
The CVE record for CVE-2026-106972 was published on October 28, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 30, 2026; the record at its source may have been updated since.
Is CVE-2026-106972 actively exploited?
CVE-2026-106972 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (27th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-106972?
CVE-2026-106972 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-106972?
A fix for CVE-2026-106972 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-106972 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-106972

Explore →

Is Your Infrastructure Affected by CVE-2026-106972?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.