Skip to main content
Mallory
Medium

Improper Neutralization of Attacker-Controlled Input in Go net/textproto Error Messages

IdentifiersCVE-2026-42507CWE-117

CVE-2026-42507 affects the Go standard library net/textproto package. When returning errors, affected functions included attacker-controlled input directly in the error text without escaping or neutralization. In normal usage, this input may originate from external parties, such as data parsed from remote servers; for example, net/http clients use ReadMIMEHeader when parsing headers received from a server. Because the raw input was embedded in returned errors, a malicious peer could cause arbitrary content to appear in application error output or logs. The issue is specifically an error-handling flaw in which untrusted input is reflected into error messages without sanitization.

Share:
For your environment

Are you exposed to this one?

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.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows an attacker to inject misleading or maliciously crafted content into logs, console output, or other sinks that record or display returned errors. This can enable log injection/forgery, corruption of operational visibility, and inclusion of terminal control bytes or escape sequences in printed output. The primary impact is integrity of logs and operator-facing output rather than direct code execution.

Mitigation

If you can’t patch tonight, do this now.

If immediate upgrade is not possible, avoid directly logging or printing raw error strings originating from net/textproto parsing of untrusted input. Sanitize, escape, or encode control characters and line breaks before writing errors to logs, terminals, or other operator-visible outputs. Treat protocol parsing errors derived from remote input as untrusted data.

Remediation

Patch, then assume compromise.

Upgrade to a patched Go release that includes the fix for CVE-2026-42507. The provided context states the issue was fixed in Go 1.26.4 and Go 1.25.11. Applications should rebuild against one of these or later patched versions.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
GolangGoapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

6 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

No news coverage yet. Advisories and community discussion only.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity6

Community discussion across Reddit, Mastodon, and other social sources.