CVE-2026-27144

HIGHNVD 7.17.1
EchelonGraph scoreMEDIUM confidence

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

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week
7.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 7.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

The compiler is meant to unwrap pointers which are the operands of a memory move; a no-op interface conversion prevented the compiler from making the correct determination about non-overlapping moves, potentially leading to memory corruption at runtime.

CVSS v3
7.1
EG Score
7.1HIGHmedium confidence
EG Risk
32
EG Risk 32/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)
Severity71% × 45%
The EG Score, 7.1 of 10.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (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.
EPSS PROB
0.3%
EPSS %ILE
16th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (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

April 8, 2026

Last Modified

July 25, 2026

Advisory Details (4)

Auto-updated Jul 25, 2026
Patch available.
Web page

GO-2026-4867 - Go Packages

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

cmd/compile: no-op interface conversion bypasses overlap checking · Issue #78371 · golang/go · GitHub

https://go.dev/issue/78371

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

Weakness Classification(1)

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

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

Showing the most recent 97 of 251 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 154 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.3% · 16th percentile
  2. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  3. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  4. 2026-10-12 16:17 UTCEG score recompute
  5. 2026-10-11 20:00 UTCEG score recompute
  6. 2026-10-11 17:13 UTCEG score recompute
  7. 2026-10-11 14:44 UTCEG score recompute
  8. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  9. 2026-10-10 22:17 UTCOSV refresh
  10. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  11. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  12. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  13. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  14. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  15. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  16. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  17. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  18. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  19. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  20. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  21. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  22. 2026-09-26 00:26 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  23. 2026-09-21 10:19 UTCOSV refresh
  24. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  25. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.3% · 18th percentile
Show 72 more
  1. 2026-09-17 19:30 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  2. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  3. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  4. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  5. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  6. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  7. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  8. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  9. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  10. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  11. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  12. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  13. 2026-09-02 08:44 UTCOSV refresh
  14. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  15. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  16. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  17. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  18. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  19. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  20. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  21. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  22. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  23. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  24. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  25. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  26. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  27. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  28. 2026-08-16 07:52 UTCEG score recompute
  29. 2026-08-16 07:52 UTCVendor advisory
  30. 2026-08-16 07:52 UTCGHSA enrichmentGHSA-cqrx-3m42-5p5w · GitHub severity HIGH · GitHub CVSS 7.1
  31. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  32. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  33. 2026-08-14 18:30 UTCVendor advisory
  34. 2026-08-14 18:30 UTCGHSA enrichmentGHSA-cqrx-3m42-5p5w · GitHub severity HIGH · GitHub CVSS 7.1
  35. 2026-08-14 05:21 UTCEG score recompute
  36. 2026-08-14 05:21 UTCVendor advisory
  37. 2026-08-14 05:21 UTCGHSA enrichmentGHSA-cqrx-3m42-5p5w · GitHub severity HIGH · GitHub CVSS 7.1
  38. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  39. 2026-08-13 09:37 UTCVendor advisory
  40. 2026-08-13 09:37 UTCGHSA enrichmentGHSA-cqrx-3m42-5p5w · GitHub severity HIGH · GitHub CVSS 7.1
  41. 2026-08-12 19:36 UTCEG score recompute
  42. 2026-08-12 19:36 UTCVendor advisory
  43. 2026-08-12 19:36 UTCGHSA enrichmentGHSA-cqrx-3m42-5p5w · GitHub severity HIGH · GitHub CVSS 7.1
  44. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  45. 2026-08-11 19:49 UTCEG score recompute
  46. 2026-08-11 19:49 UTCVendor advisory
  47. 2026-08-11 19:49 UTCGHSA enrichmentGHSA-cqrx-3m42-5p5w · GitHub severity HIGH · GitHub CVSS 7.1
  48. 2026-08-11 13:42 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  49. 2026-08-11 03:11 UTCEG score recompute
  50. 2026-08-11 03:11 UTCVendor advisory
  51. 2026-08-11 03:11 UTCGHSA enrichmentGHSA-cqrx-3m42-5p5w · GitHub severity HIGH · GitHub CVSS 7.1
  52. 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  53. 2026-08-10 06:49 UTCVendor advisory
  54. 2026-08-10 06:48 UTCGHSA enrichmentGHSA-cqrx-3m42-5p5w · GitHub severity HIGH · GitHub CVSS 7.1
  55. 2026-08-09 17:51 UTCEG score recompute
  56. 2026-08-09 17:51 UTCVendor advisory
  57. 2026-08-09 17:50 UTCGHSA enrichmentGHSA-cqrx-3m42-5p5w · GitHub severity HIGH · GitHub CVSS 7.1
  58. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  59. 2026-08-09 04:52 UTCEG score recompute
  60. 2026-08-09 04:52 UTCVendor advisory
  61. 2026-08-09 04:52 UTCGHSA enrichmentGHSA-cqrx-3m42-5p5w · GitHub severity HIGH · GitHub CVSS 7.1
  62. 2026-08-08 16:37 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  63. 2026-08-08 03:50 UTCEG score recompute
  64. 2026-08-08 03:50 UTCVendor advisory
  65. 2026-08-08 03:50 UTCGHSA enrichmentGHSA-cqrx-3m42-5p5w · GitHub severity HIGH · GitHub CVSS 7.1
  66. 2026-08-07 14:52 UTCEG score recompute
  67. 2026-08-07 14:52 UTCVendor advisory
  68. 2026-08-07 14:51 UTCGHSA enrichmentGHSA-cqrx-3m42-5p5w · GitHub severity HIGH · GitHub CVSS 7.1
  69. 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  70. 2026-08-06 12:56 UTCVendor advisory
  71. 2026-08-06 12:56 UTCGHSA enrichmentGHSA-cqrx-3m42-5p5w · GitHub severity HIGH · GitHub CVSS 7.1
  72. 2026-08-05 23:57 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-27144?
CVE-2026-27144 is a high-severity vulnerability; its CVE record was published on April 8, 2026. The compiler is meant to unwrap pointers which are the operands of a memory move; a no-op interface conversion prevented the compiler from making the correct determination about non-overlapping moves, potentially leading to memory corruption at runtime.
When was the CVE record for CVE-2026-27144 published?
The CVE record for CVE-2026-27144 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-27144 actively exploited?
CVE-2026-27144 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (16th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-27144?
CVE-2026-27144 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-27144?
A fix for CVE-2026-27144 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-27144 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-27144

Explore →

Is Your Infrastructure Affected by CVE-2026-27144?

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