Secuno
ENNL
Book demo

CVE-2026-27140

Golang Go broken access control

8.8 HIGHEPSS 0.66%
  1. Published8 Apr 2026

Description

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 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredNone
User interactionRequired
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Affected products

Golang Go≥ 1.26.0 < 1.26.2 · < 1.25.9

Remediation

Fixed in
Golang Go≥ 1.26.2
Patch & vendor advisories

References

and 14 more references

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-163018.5
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.7 before…
CVE-2026-1095598.7
EdgeEver Desktop 1.6.26 through 1.112.0 contains a navigation allowlist bypass that…
CVE-2026-773669.9
obsidian-tc is a governed, agent-ready Model Context Protocol server for Obsidian…
CVE-2026-1039038.8
An incorrect authorization vulnerability in the WinBox authentication flow of MikroTik…
CVE-2026-1087468.8
Vearch 3.5.2 through 3.5.9 contains an incorrect authorization vulnerability in…
CVE-2026-816499.1
The Fundiin cho WooCommerce WordPress plugin through 3.4.0 does not have proper…

Frequently asked

Is CVE-2026-27140 being actively exploited?

CVE-2026-27140 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.66%.

How severe is CVE-2026-27140?

CVE-2026-27140 has a CVSS 3.1 base score of 8.8, rated high. EPSS estimates a 0.66% probability of exploitation.

Which products are affected by CVE-2026-27140?

Affected products include Golang Go.

How do I fix CVE-2026-27140?

Upgrade affected software to a fixed version, for example Golang Go 1.26.2 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-27140 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.