CVE-2026-130849

CRITICALPre-NVD 9.89.8
EchelonGraph scoreHIGH confidence

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

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-11-17. A secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-127253 (ENISA EUVD) · GHSA-9q5f-g948-c95m (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
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).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

BZFlag bzfs before 2.4.32 contains a heap out-of-bounds write vulnerability in NetHandler::tcpReceive() that allows remote unauthenticated attackers to corrupt heap memory by sending a TCP message with a body length of exactly 1024. Attackers can overwrite the tcplen receive offset with a negative value to write controlled bytes before the buffer, crashing the server or executing commands as the bzfs user.

CVSS v3
9.8
EG Score
9.8CRITICALhigh confidence
EG Risk
59
EG Risk 59/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)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
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 none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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.5%
EPSS %ILE
43rd
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 (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-21). 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: 3 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 none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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)3 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 total (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

November 17, 2026

Last Modified

November 19, 2026

Advisory Details (4)

Auto-updated Nov 19, 2026
Patch available. Sources: github_commit, github_release.
Web page

BZFlag bzfs before 2.4.32 Heap Out-of-Bounds Write via NetHandler::tcpReceive() | Advisories | VulnCheck

https://www.vulncheck.com/advisories/bzflag-bzfs-before-2.4.32-heap-out-of-bounds-write-via-nethandler-tcpreceive
GitHub release Patch Available

2.4.32 "A Narrow Escape"

Patch available: BZFlag-Dev/bzflag v2.4.32

https://github.com/BZFlag-Dev/bzflag/releases/tag/v2.4.32
GitHub commit Patch Available

commit 8e501d685aef (BZFlag-Dev/bzflag)

Patch available: BZFlag-Dev/bzflag v2.4.32 (contains commit 8e501d685aef)

https://github.com/BZFlag-Dev/bzflag/commit/8e501d685aef549090b363260979a4eb93484ea1
Web page

bzflag/src/game/NetHandler.cxx at v2.4.30 · BZFlag-Dev/bzflag · GitHub

https://github.com/BZFlag-Dev/bzflag/blob/v2.4.30/src/game/NetHandler.cxx#L575-L640

Vendor Advisories for CVE-2026-130849(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 12× in last 7d / 12× 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-21 21:56 UTCEchelonGraph re-scored
  2. 2026-11-21 21:56 UTCGHSA enrichmentGHSA-9q5f-g948-c95m · GitHub severity CRITICAL · GitHub CVSS 9.8
  3. 2026-11-21 16:38 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  4. 2026-11-20 22:36 UTCEchelonGraph re-scored
  5. 2026-11-20 22:36 UTCGHSA enrichmentGHSA-9q5f-g948-c95m · GitHub severity CRITICAL · GitHub CVSS 9.8
  6. 2026-11-20 16:36 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  7. 2026-11-19 23:17 UTCEchelonGraph re-scored
  8. 2026-11-19 23:17 UTCGHSA enrichmentGHSA-9q5f-g948-c95m · GitHub severity CRITICAL · GitHub CVSS 9.8
  9. 2026-11-19 16:33 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  10. 2026-11-19 04:20 UTCEchelonGraph re-scored
  11. 2026-11-19 04:20 UTCGHSA enrichmentGHSA-9q5f-g948-c95m · GitHub severity CRITICAL · GitHub CVSS 9.8
  12. 2026-11-18 21:08 UTCEchelonGraph re-scored
  13. 2026-11-18 21:08 UTCGHSA enrichmentGHSA-9q5f-g948-c95m · GitHub severity CRITICAL · GitHub CVSS 9.8
  14. 2026-11-18 16:34 UTCEPSS rescoreEPSS 0.8% · 58th percentile
  15. 2026-11-17 21:49 UTCEchelonGraph re-scored
  16. 2026-11-17 21:49 UTCGHSA enrichmentGHSA-9q5f-g948-c95m · GitHub severity CRITICAL · GitHub CVSS 9.8
  17. 2026-11-17 21:03 UTCENISA EUVD ID recordedEUVD-2026-127253 · Source: ENISA EUVD
  18. 2026-11-17 20:28 UTCEchelonGraph re-scored
  19. 2026-11-17 19:55 UTCEchelonGraph re-scoredFirst assessed: 9.8 CRITICAL
  20. 2026-11-17 19:52 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-130849?
CVE-2026-130849 is a critical-severity vulnerability; its CVE record was published on November 17, 2026. BZFlag bzfs before 2.4.32 contains a heap out-of-bounds write vulnerability in NetHandler::tcpReceive() that allows remote unauthenticated attackers to corrupt heap memory by sending a TCP message with a body length of exactly 1024. Attackers can overwrite the tcplen receive offset with a negative…
When was CVE-2026-130849 made public?
CVE-2026-130849 was made public on November 17, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on November 17, 2026. EchelonGraph's copy of the record carries a last-modified date of November 19, 2026; the record at its source may have been updated since.
Is CVE-2026-130849 actively exploited?
CVE-2026-130849 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (43rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-130849?
CVE-2026-130849 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-130849?
A fix for CVE-2026-130849 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-130849 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-130849?

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