CVE-2026-27140

HIGHNVD 8.88.8
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
8.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: 8.8Exploit: None knownExposed: 0

A fix is available — apply it.

SWIG file names containing 'cgo' and well-crafted payloads could lead to code smuggling and arbitrary code execution at build time due to trust layer bypass.

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
40(Track)
EG Risk 40/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
Severity88% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
50%
KEV
Not listed

Published

April 8, 2026

Last Modified

September 10, 2026

Advisory Details (4)

Auto-updated Jun 7, 2026
No patch confirmed yet.
generic

GO-2026-4871 - Go Packages

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

cmd/go: trust layer bypass when using cgo and SWIG · Issue #78335 · golang/go · GitHub

https://go.dev/issue/78335

Patch Availability(17)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatopenshift4/ose-docker-builder-rhel9:17867880122026-08-26redhat
redhatopenshift4/ose-docker-builder-rhel9:17867629822026-08-26redhat
redhatopenshift4/ose-docker-builder-rhel9:17870593942026-08-25redhat
redhatopenshift4/ose-docker-builder-rhel9:17821849242026-07-09redhat
redhatopenshift4/ose-docker-builder-rhel9:17809782722026-06-17redhat
redhatopenshift4/ovirt-csi-driver-rhel9-operator:17800449102026-06-10redhat
redhatgo-toolset:rhel8-8060020260505152018.97d7f71f2026-05-13redhat
redhatgo-toolset:rhel8-8040020260505161557.5081a2622026-05-13redhat
redhatgo-toolset:rhel8-8080020260506150958.6b4b45d82026-05-13redhat
redhatgolang-0:1.17.13-12.el9_02026-05-12redhat
redhatgolang-0:1.19.13-25.el9_22026-05-12redhat
redhatgolang-0:1.21.13-16.el9_42026-05-12redhat
redhatgolang-0:1.25.9-1.el9_62026-05-11redhat
redhatgolang-0:1.25.9-1.el10_02026-05-11redhat
redhatgo-toolset:rhel8-8100020260422204008.a3795dee2026-04-27redhat
redhatgolang-0:1.25.9-1.el9_72026-04-24redhat
redhatgolang-0:1.25.9-3.el10_12026-04-23redhat

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

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 48× 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 255 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-27140?
CVE-2026-27140 is a high vulnerability published on April 8, 2026. SWIG file names containing 'cgo' and well-crafted payloads could lead to code smuggling and arbitrary code execution at build time due to trust layer bypass.
When was CVE-2026-27140 disclosed?
CVE-2026-27140 was first published in the National Vulnerability Database on April 8, 2026, with the most recent update on September 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-27140 actively exploited?
CVE-2026-27140 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 50.4% of all scored CVEs.
What is the CVSS score of CVE-2026-27140?
CVE-2026-27140 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-27140?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-27140, 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-27140

Explore →

Is Your Infrastructure Affected by CVE-2026-27140?

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