CVE-2025-61731 is an argument-injection vulnerability in the Go cmd/go toolchain's CgoPkgConfig handling. When building malicious Go source code, the toolchain permits pkg-config arguments that are not explicitly safelisted through the "#cgo pkg-config:" directive. An attacker can supply the "--log-file" option to cause pkg-config to write to an attacker-selected location with partial control over the written content. The flag-sanitization bypass is also associated with potential arbitrary code execution, although the specific code-execution mechanism is not established.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
34 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Go toolchain (cmd/go) code execution risk via CgoPkgConfig flag sanitization bypass, allowing malicious parameters to influence pkg-config invocation and potentially lead to unintended command execution or dangerous compiler/linker option injection in build environments.
An arbitrary code execution risk in Go’s cmd/go where CgoPkgConfig can bypass flag sanitization and invoke pkg-config with unsafe inputs.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.