RHSA-2026:22112

Pathological inputs could cause DoS through consumePhrase when parsing an email address according to RFC 5322.

The Dial and LookupPort functions panic on Windows when provided with an input containing a NUL (0).

Well-crafted inputs reaching ParseAddress, ParseAddressList, and ParseDate were able to trigger excessive CPU exhaustion and memory allocations.

When processing HTTP/2 SETTINGS frames, transport will enter an infinite loop of writing CONTINUATION frames if it receives a SETTINGS_MAX_FRAME_SIZE with a value of 0.

When using LookupCNAME with the cgo DNS resolver, a very long CNAME response can trigger a double-free of C memory and a crash.

A malicious module proxy can exploit a flaw in the go command's validation of module checksums to bypass checksum database validation.

ReverseProxy can forward queries containing parameters not visible to Rewrite functions.

If a trusted template author were to write a <script> tag containing an empty 'type' attribute or a 'type' attribute with an ASCII whitespace, the execution of the template would incorrectly escape any data passed into t…

CVE-2026-27142 fixed a vulnerability in which URLs were not correctly escaped inside of a <meta> tag's <content> attribute.

Context was not properly tracked across template branches for JS template literals, leading to possibly incorrect escaping of content when branches were used.

The "go tool pack" subcommand (usually used only by the compiler as an internal tool with known-good inputs) does not sanitize output filenames.

tar.Reader can allocate an unbounded amount of memory when reading a maliciously-crafted archive containing a large number of sparse regions encoded in the "old GNU sparse map" format.

The "go bug" command writes to two files with predictable names in the system temporary directory (for example, "/tmp").