CVE-2026-27143

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-04-08. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 5 sources updated this week
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.7%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Arithmetic over induction variables in loops were not correctly checked for underflow or overflow. As a result, the compiler would allow for invalid indexing to occur at runtime, potentially leading to memory corruption.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
59
EG Risk 59/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)
Severity98% × 45%
The EG Score, 9.8 of 10.
Exploitation0.7% × 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.7%
EPSS %ILE
50th
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 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.

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

April 8, 2026

Last Modified

July 25, 2026

Advisory Details (4)

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

GO-2026-4868 - Go Packages

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

cmd/compile: possible memory corruption after bound check elimination · Issue #78333 · golang/go · GitHub

https://go.dev/issue/78333

Patch Availability(22)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(6 across 5 ecosystems)
Debian:14(2)
PackageVulnerable rangeFix by version rangeDependents
golang-1.251.25.0-1 ... 1.25.8-1 (9 versions)
  • every version up to 1.25.9-1: fixed in 1.25.9-1
—
golang-1.261.26.0-1, 1.26.1-1, 1.26~rc2-1, 1.26~rc3-1, 1.26~rc3-2
  • every version up to 1.26.2-1: fixed in 1.26.2-1
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
golang-1.151.15.15-1 ... 1.15.9-6 (10 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
golang-1.191.19.10-1 ... 1.19.9-1 (12 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
golang-1.241.24.12-1 ... 1.24.9-1 (10 versions)
  • every version on: no fix on record
—
Go(1)
PackageVulnerable rangeFix by version rangeDependents
toolchain—
  • every version up to 1.25.9: fixed in 1.25.9
  • 1.26.0-0 up to 1.26.2: fixed in 1.26.2
—

Additional Vendor Advisories

(3)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 20× in last 7d / 36× 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.

Showing the most recent 97 of 357 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 3 repeat rows among the latest 100 are merged into the row they repeat. The 260 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  2. 2026-10-14 11:14 UTCEG score recompute
  3. 2026-10-14 11:14 UTCVendor advisory
  4. 2026-10-14 11:14 UTCGHSA enrichmentGHSA-cfp9-33rc-j74f · GitHub severity CRITICAL · GitHub CVSS 9.8
  5. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  6. 2026-10-13 10:02 UTCEG score recompute
  7. 2026-10-13 10:02 UTCVendor advisory
  8. 2026-10-13 10:02 UTCGHSA enrichmentGHSA-cfp9-33rc-j74f · GitHub severity CRITICAL · GitHub CVSS 9.8
  9. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  10. 2026-10-12 16:17 UTCEG score recompute
  11. 2026-10-12 08:54 UTCVendor advisory
  12. 2026-10-12 08:53 UTCGHSA enrichmentGHSA-cfp9-33rc-j74f · GitHub severity CRITICAL · GitHub CVSS 9.8
  13. 2026-10-11 20:00 UTCEG score recompute
  14. 2026-10-11 17:13 UTCEG score recompute
  15. 2026-10-11 14:44 UTCEG score recompute
  16. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  17. 2026-10-11 10:14 UTCOSV refresh
  18. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  19. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  20. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  21. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  22. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  23. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  24. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  25. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.7% · 49th percentile
Show 72 more
  1. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  2. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  3. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  4. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  5. 2026-09-26 00:26 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  6. 2026-09-21 22:45 UTCOSV refresh
  7. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  8. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  9. 2026-09-17 19:30 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  10. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  11. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  12. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  13. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  14. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  15. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  16. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  17. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  18. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  19. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  20. 2026-09-02 18:38 UTCOSV refresh
  21. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  22. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  23. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  24. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  25. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  26. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  27. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  28. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  29. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  30. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  31. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  32. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  33. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  34. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  35. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  36. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  37. 2026-08-16 11:30 UTCVendor advisory
  38. 2026-08-16 11:30 UTCGHSA enrichmentGHSA-cfp9-33rc-j74f · GitHub severity CRITICAL · GitHub CVSS 9.8
  39. 2026-08-16 07:52 UTCEG score recompute
  40. 2026-08-16 07:52 UTCVendor advisory
  41. 2026-08-16 07:52 UTCGHSA enrichmentGHSA-cfp9-33rc-j74f · GitHub severity CRITICAL · GitHub CVSS 9.8
  42. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  43. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  44. 2026-08-14 23:32 UTCVendor advisory
  45. 2026-08-14 23:32 UTCGHSA enrichmentGHSA-cfp9-33rc-j74f · GitHub severity CRITICAL · GitHub CVSS 9.8
  46. 2026-08-14 19:54 UTCVendor advisory
  47. 2026-08-14 19:54 UTCGHSA enrichmentGHSA-cfp9-33rc-j74f · GitHub severity CRITICAL · GitHub CVSS 9.8
  48. 2026-08-14 16:16 UTCVendor advisory
  49. 2026-08-14 16:16 UTCGHSA enrichmentGHSA-cfp9-33rc-j74f · GitHub severity CRITICAL · GitHub CVSS 9.8
  50. 2026-08-14 12:37 UTCVendor advisory
  51. 2026-08-14 12:37 UTCGHSA enrichmentGHSA-cfp9-33rc-j74f · GitHub severity CRITICAL · GitHub CVSS 9.8
  52. 2026-08-14 08:59 UTCVendor advisory
  53. 2026-08-14 08:59 UTCGHSA enrichmentGHSA-cfp9-33rc-j74f · GitHub severity CRITICAL · GitHub CVSS 9.8
  54. 2026-08-14 05:21 UTCEG score recompute
  55. 2026-08-14 05:21 UTCVendor advisory
  56. 2026-08-14 05:21 UTCGHSA enrichmentGHSA-cfp9-33rc-j74f · GitHub severity CRITICAL · GitHub CVSS 9.8
  57. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  58. 2026-08-13 09:37 UTCVendor advisory
  59. 2026-08-13 09:37 UTCGHSA enrichmentGHSA-cfp9-33rc-j74f · GitHub severity CRITICAL · GitHub CVSS 9.8
  60. 2026-08-13 02:52 UTCVendor advisory
  61. 2026-08-13 02:52 UTCGHSA enrichmentGHSA-cfp9-33rc-j74f · GitHub severity CRITICAL · GitHub CVSS 9.8
  62. 2026-08-12 23:14 UTCVendor advisory
  63. 2026-08-12 23:14 UTCGHSA enrichmentGHSA-cfp9-33rc-j74f · GitHub severity CRITICAL · GitHub CVSS 9.8
  64. 2026-08-12 19:36 UTCEG score recompute
  65. 2026-08-12 19:36 UTCVendor advisory
  66. 2026-08-12 19:36 UTCGHSA enrichmentGHSA-cfp9-33rc-j74f · GitHub severity CRITICAL · GitHub CVSS 9.8
  67. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  68. 2026-08-11 23:27 UTCVendor advisory
  69. 2026-08-11 23:27 UTCGHSA enrichmentGHSA-cfp9-33rc-j74f · GitHub severity CRITICAL · GitHub CVSS 9.8
  70. 2026-08-11 19:49 UTCEG score recompute
  71. 2026-08-11 19:49 UTCVendor advisory
  72. 2026-08-11 19:49 UTCGHSA enrichmentGHSA-cfp9-33rc-j74f · GitHub severity CRITICAL · GitHub CVSS 9.8

Frequently asked(5)

What is CVE-2026-27143?
CVE-2026-27143 is a critical-severity vulnerability; its CVE record was published on April 8, 2026. Arithmetic over induction variables in loops were not correctly checked for underflow or overflow. As a result, the compiler would allow for invalid indexing to occur at runtime, potentially leading to memory corruption.
When was the CVE record for CVE-2026-27143 published?
The CVE record for CVE-2026-27143 was published on April 8, 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 July 25, 2026; the record at its source may have been updated since.
Is CVE-2026-27143 actively exploited?
CVE-2026-27143 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (50th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-27143?
CVE-2026-27143 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-27143?
A fix for CVE-2026-27143 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-27143 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-27143

Explore →

Is Your Infrastructure Affected by CVE-2026-27143?

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