CVE-2026-56851

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-07. 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
Trending — 5 sources updated this week
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).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

The Nickname profile can panic with an out-of-bounds slice error when transforming crafted input into a short destination buffer.

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

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
The EG Score, 7.5 of 10.
Exploitation0.3% × 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 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
25th
KEV
Not listed

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

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 7, 2026

Last Modified

October 8, 2026

Advisory Details (3)

Auto-updated Oct 8, 2026
Patch available.
Web page

GO-2026-6629 - Go Packages

https://pkg.go.dev/vuln/GO-2026-6629
Web page

x/text/secure/precis: panic parsing crafted input in nickAdditionalMapping.Transform() · Issue #80112 · golang/go · GitHub

https://go.dev/issue/80112
Web page
https://go.dev/cl/793360

Vendor Advisories for CVE-2026-56851(2)

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

Affected Packages

(4 across 4 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
golang-golang-x-text0.10.0-1 ... 0.9.0-1 (21 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
golang-golang-x-text0.22.0-1 ... 0.41.0-1 (10 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
golang-golang-x-text0.22.0-1 ... 0.40.0-1 (9 versions)
  • every version up to 0.41.0-1: fixed in 0.41.0-1
—
Go(1)
PackageVulnerable rangeFix by version rangeDependents
golang.org/x/text—
  • every version up to 0.41.0: fixed in 0.41.0
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 28× in last 7d / 28× 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 it from the CNA feed. 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). Most recent first.

  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  3. 2026-10-12 15:54 UTCEG score recompute
  4. 2026-10-12 04:12 UTCGHSA enrichmentGHSA-gx9w-9qq8-m485 · GitHub severity HIGH · GitHub CVSS 7.5
  5. 2026-10-11 19:37 UTCEG score recompute
  6. 2026-10-11 16:53 UTCEG score recompute
  7. 2026-10-11 15:13 UTCGHSA enrichmentGHSA-gx9w-9qq8-m485 · GitHub severity HIGH · GitHub CVSS 7.5
  8. 2026-10-11 14:15 UTCEG score recompute
  9. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  10. 2026-10-11 02:16 UTCEG score recompute
  11. 2026-10-11 02:15 UTCGHSA enrichmentGHSA-gx9w-9qq8-m485 · GitHub severity HIGH · GitHub CVSS 7.5
  12. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  13. 2026-10-10 13:14 UTCGHSA enrichmentGHSA-gx9w-9qq8-m485 · GitHub severity HIGH · GitHub CVSS 7.5
  14. 2026-10-10 00:17 UTCEG score recompute
  15. 2026-10-10 00:16 UTCGHSA enrichmentGHSA-gx9w-9qq8-m485 · GitHub severity HIGH · GitHub CVSS 7.5
  16. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  17. 2026-10-09 11:19 UTCGHSA enrichmentGHSA-gx9w-9qq8-m485 · GitHub severity HIGH · GitHub CVSS 7.5
  18. 2026-10-08 21:39 UTCEG score recompute
  19. 2026-10-08 21:38 UTCGHSA enrichmentGHSA-gx9w-9qq8-m485 · GitHub severity HIGH · GitHub CVSS 7.5
  20. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  21. 2026-10-08 14:56 UTCGHSA enrichmentGHSA-gx9w-9qq8-m485
  22. 2026-10-08 13:52 UTCEG score recomputeFirst assessed: 7.5 HIGH
  23. 2026-10-08 13:52 UTCGHSA enrichmentGHSA-gx9w-9qq8-m485
  24. 2026-10-08 13:51 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
  25. 2026-10-07 18:38 UTCGHSA enrichmentGHSA-gx9w-9qq8-m485
Show 3 more
  1. 2026-10-07 18:37 UTCNVD update
  2. 2026-10-07 17:57 UTCEG score recompute
  3. 2026-10-07 17:56 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-56851?
CVE-2026-56851 is a high-severity vulnerability; its CVE record was published on October 7, 2026. The Nickname profile can panic with an out-of-bounds slice error when transforming crafted input into a short destination buffer.
When was the CVE record for CVE-2026-56851 published?
The CVE record for CVE-2026-56851 was published on October 7, 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 8, 2026; the record at its source may have been updated since.
Is CVE-2026-56851 actively exploited?
CVE-2026-56851 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (25th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-56851?
CVE-2026-56851 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-56851?
A fix for CVE-2026-56851 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-56851 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-56851

Explore →

Is Your Infrastructure Affected by CVE-2026-56851?

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

Book a Demo →Browse All CVEs