CVE-2026-27143

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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, ghsa, nvd
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.8Exploit: None knownExposed: 0

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.8(medium)
EG Risk
59(Track)
EG Risk 59/100SSVC: Track

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
Severity98% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
43%
KEV
Not listed

Published

April 8, 2026

Last Modified

July 25, 2026

Advisory Details (4)

Auto-updated Aug 29, 2026
No patch confirmed yet.
generic

GO-2026-4868 - Go Packages

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

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

https://go.dev/issue/78333

Patch Availability(19)

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 rangeFixed inDependents
golang-1.251.25.0-1 ... 1.25.8-1 (9 versions)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-21.26.2-1
Debian:11(1)
PackageVulnerable rangeFixed inDependents
golang-1.151.15.15-1 ... 1.15.9-6 (10 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
golang-1.191.19.10-1 ... 1.19.9-1 (12 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
golang-1.241.24.12-1 ... 1.24.9-1 (10 versions)
Go(1)
PackageVulnerable rangeFixed inDependents
toolchain1.26.2

Additional Vendor Advisories

(1)

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 6× in last 7d / 125× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 309 total refreshes for this CVE.

  1. 2026-08-30 19:17 UTCEPSS rescore
  2. 2026-08-30 01:22 UTCEPSS rescore
  3. 2026-08-28 21:41 UTCEPSS rescore
  4. 2026-08-27 14:25 UTCEPSS rescore
  5. 2026-08-26 14:46 UTCEPSS rescore
  6. 2026-08-25 13:48 UTCEPSS rescore
  7. 2026-08-23 00:19 UTCEPSS rescore
  8. 2026-08-21 23:49 UTCEPSS rescore
  9. 2026-08-20 22:55 UTCEPSS rescore
  10. 2026-08-19 17:03 UTCEPSS rescore
  11. 2026-08-18 13:48 UTCEPSS rescore
  12. 2026-08-17 13:47 UTCEPSS rescore
  13. 2026-08-16 14:56 UTCEPSS rescore
  14. 2026-08-16 11:30 UTCVendor advisory
  15. 2026-08-16 11:30 UTCGHSA enrichment
  16. 2026-08-16 07:52 UTCEG score recompute
  17. 2026-08-16 07:52 UTCVendor advisory
  18. 2026-08-16 07:52 UTCGHSA enrichment
  19. 2026-08-16 02:14 UTCEPSS rescore
  20. 2026-08-15 01:30 UTCEPSS rescore
  21. 2026-08-14 23:32 UTCVendor advisory
  22. 2026-08-14 23:32 UTCGHSA enrichment
  23. 2026-08-14 19:54 UTCVendor advisory
  24. 2026-08-14 19:54 UTCGHSA enrichment
  25. 2026-08-14 16:16 UTCVendor advisory
Show 75 more
  1. 2026-08-14 16:16 UTCGHSA enrichment
  2. 2026-08-14 12:37 UTCVendor advisory
  3. 2026-08-14 12:37 UTCGHSA enrichment
  4. 2026-08-14 08:59 UTCVendor advisory
  5. 2026-08-14 08:59 UTCGHSA enrichment
  6. 2026-08-14 05:21 UTCEG score recompute
  7. 2026-08-14 05:21 UTCVendor advisory
  8. 2026-08-14 05:21 UTCGHSA enrichment
  9. 2026-08-13 22:00 UTCEPSS rescore
  10. 2026-08-13 09:37 UTCVendor advisory
  11. 2026-08-13 09:37 UTCGHSA enrichment
  12. 2026-08-13 02:52 UTCVendor advisory
  13. 2026-08-13 02:52 UTCGHSA enrichment
  14. 2026-08-12 23:14 UTCVendor advisory
  15. 2026-08-12 23:14 UTCGHSA enrichment
  16. 2026-08-12 19:36 UTCEG score recompute
  17. 2026-08-12 19:36 UTCVendor advisory
  18. 2026-08-12 19:36 UTCGHSA enrichment
  19. 2026-08-12 13:50 UTCEPSS rescore
  20. 2026-08-11 23:27 UTCVendor advisory
  21. 2026-08-11 23:27 UTCGHSA enrichment
  22. 2026-08-11 19:49 UTCEG score recompute
  23. 2026-08-11 19:49 UTCVendor advisory
  24. 2026-08-11 19:49 UTCGHSA enrichment
  25. 2026-08-11 13:42 UTCEPSS rescore
  26. 2026-08-11 06:50 UTCVendor advisory
  27. 2026-08-11 06:50 UTCGHSA enrichment
  28. 2026-08-11 03:11 UTCEG score recompute
  29. 2026-08-11 03:11 UTCVendor advisory
  30. 2026-08-11 03:11 UTCGHSA enrichment
  31. 2026-08-11 00:00 UTCEPSS rescore
  32. 2026-08-10 11:56 UTCVendor advisory
  33. 2026-08-10 11:56 UTCGHSA enrichment
  34. 2026-08-10 07:01 UTCVendor advisory
  35. 2026-08-10 07:01 UTCGHSA enrichment
  36. 2026-08-10 03:23 UTCVendor advisory
  37. 2026-08-10 03:23 UTCGHSA enrichment
  38. 2026-08-09 23:45 UTCVendor advisory
  39. 2026-08-09 23:45 UTCGHSA enrichment
  40. 2026-08-09 20:07 UTCVendor advisory
  41. 2026-08-09 20:07 UTCGHSA enrichment
  42. 2026-08-09 16:29 UTCEG score recompute
  43. 2026-08-09 16:29 UTCVendor advisory
  44. 2026-08-09 16:28 UTCGHSA enrichment
  45. 2026-08-09 13:46 UTCEPSS rescore
  46. 2026-08-09 12:51 UTCVendor advisory
  47. 2026-08-09 12:50 UTCGHSA enrichment
  48. 2026-08-09 08:31 UTCVendor advisory
  49. 2026-08-09 08:30 UTCGHSA enrichment
  50. 2026-08-09 04:52 UTCEG score recompute
  51. 2026-08-09 04:52 UTCVendor advisory
  52. 2026-08-09 04:52 UTCGHSA enrichment
  53. 2026-08-08 16:37 UTCEPSS rescore
  54. 2026-08-08 09:28 UTCVendor advisory
  55. 2026-08-08 09:28 UTCGHSA enrichment
  56. 2026-08-08 05:50 UTCVendor advisory
  57. 2026-08-08 05:50 UTCGHSA enrichment
  58. 2026-08-08 02:12 UTCVendor advisory
  59. 2026-08-08 02:12 UTCGHSA enrichment
  60. 2026-08-07 22:34 UTCVendor advisory
  61. 2026-08-07 22:34 UTCGHSA enrichment
  62. 2026-08-07 18:56 UTCEG score recompute
  63. 2026-08-07 18:56 UTCVendor advisory
  64. 2026-08-07 18:56 UTCGHSA enrichment
  65. 2026-08-07 14:52 UTCVendor advisory
  66. 2026-08-07 14:51 UTCGHSA enrichment
  67. 2026-08-06 17:35 UTCEG score recompute
  68. 2026-08-06 17:35 UTCVendor advisory
  69. 2026-08-06 17:35 UTCGHSA enrichment
  70. 2026-08-06 13:46 UTCEPSS rescore
  71. 2026-08-06 12:53 UTCVendor advisory
  72. 2026-08-06 12:53 UTCGHSA enrichment
  73. 2026-08-06 07:13 UTCVendor advisory
  74. 2026-08-06 07:12 UTCGHSA enrichment
  75. 2026-08-06 03:35 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-27143?
CVE-2026-27143 is a critical vulnerability 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 CVE-2026-27143 disclosed?
CVE-2026-27143 was first published in the National Vulnerability Database on April 8, 2026, with the most recent update on July 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-27143 actively exploited?
CVE-2026-27143 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 57.0% of all 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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-27143, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.