dbcve.org
GoApplication · Golang

CVE-2026-27140

HIGH · 8.8 CVSS v3.1 Published 2026-04-08
Fix available
A fix is available. Upgrade to 1.25.9 / 1.26.2 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is a vulnerability in SWIG (Simplified Wrapper and Interface Generator) where specially crafted file names containing 'cgo' can bypass trust validation mechanisms, allowing malicious payloads to smuggle code that executes during the build process, leading to arbitrary code execution.

MitigationUsers should restrict processing of untrusted SWIG interface files and monitor for updates/patches from the SWIG project; avoid using SWIG with files from untrusted sources until patched.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
GoApplication
Affected:< 1.25.9>= 1.26.0, < 1.26.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Go version
    Run 'go version' to determine the Go toolchain version
    Affected if Version is < 1.25.9 or >= 1.26.0 and < 1.26.2
  2. Identify SWIG usage in build process
    Search for .i SWIG interface files or usage of SWIG in build scripts, Makefiles, or CI/CD pipelines
    Affected if SWIG is being used to generate code bindings
  3. Locate files with 'cgo' in filename
    Search the project directory for files containing 'cgo' in their name (e.g., find . -name '*cgo*'), particularly .i or .swig files
    Affected if SWIG interface or input files with 'cgo' in the filename exist and are processed during build
  4. Inspect build configuration for SWIG execution
    Review build logs, scripts, or toolchain configuration to confirm SWIG is invoked during compilation
    Affected if SWIG is executed as part of the build pipeline to process cgo-related input files

You are affected if your Go version falls within the vulnerable ranges AND you use SWIG to process files with 'cgo' in the filename during build time.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.25.9 / 1.26.2 or later
Fixed in 1.25.91.26.2
Interim mitigation

Users should restrict processing of untrusted SWIG interface files and monitor for updates/patches from the SWIG project; avoid using SWIG with files from untrusted sources until patched.

Recommended fix Moderate confidence

Go 1.26.2 or later (or Go 1.25.9+ if staying on 1.25.x line)

  1. 1. Identify the current Go version by running: go version
  2. 2. If using Go < 1.25.9, upgrade to at least Go 1.25.9 or later in the 1.25.x line
  3. 3. If using Go >= 1.26.0 and < 1.26.2, upgrade to at least Go 1.26.2 or the latest 1.26.x release
  4. 4. Download the updated Go version from https://go.dev/dl/
  5. 5. Verify the upgrade by running: go version
  6. 6. Rebuild and test any projects that use SWIG interfaces to ensure the fix is applied
Caveat Minor release; review release notes for any behavioral changes. SWIG-generated code should work identically after upgrade.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Go Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,920.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-27140 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-27140 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data