Skip to main content
VulnerabilityPublished

CVE-2026-32280: golang security update

Affects golangSource GCVE Database

0
Compare

Mentioned vulnerabilities

Authoritative record:CVE-2026-32280· High 7.5

Not known to be exploited · CVSS 7.5 High : upgrade to 1.21.4-53.oe2403sp3 soon.

Data as of 11 Nov 2026, 14:50 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 1.21.4-53.oe2403sp3
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 11 Nov 2026.

What to do

Upgrade golang to 1.21.4-53.oe2403sp3.

Affected software

ProductAffectedFixed in
openEuler 24.03-LTS-SP3golangpkg:rpm/openEuler/golang&distro=openEuler-24.03-LTS-SP3Other threatsAffected
  • <1.21.4-53.oe2403sp3
Fixed in
  • 1.21.4-53.oe2403sp3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available in golang version 1.21.4-53.oe2403sp3 that addresses all listed vulnerabilities. Users and organizations should upgrade to this fixed version to mitigate these issues. No additional mitigations are indicated or required beyond applying the official update.

Description

Multiple critical security vulnerabilities have been identified in the Go programming language (golang) affecting versions prior to 1.21.4-53.oe2403sp3. These include denial of service issues in certificate chain verification, memory exhaustion via HTTP/2 Trailer headers, flow control bypass in HTTP/2, excessive CPU consumption from SETTINGS frames, improper handling of HTTP/1 CONNECT responses leading to potential request smuggling, checksum bypass in module proxy verification, and server crashes due to concurrent HPACK encoder modifications. These vulnerabilities collectively impact the integrity and availability of applications using affected Go versions.

References

Community reviews

Loading reviews…