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.17.3-53.oe2203sp4 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.17.3-53.oe2203sp4
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.17.3-53.oe2203sp4.

Affected software

ProductAffectedFixed in
openEuler 22.03-LTS-SP4golangpkg:rpm/openEuler/golang&distro=openEuler-22.03-LTS-SP4Other threatsAffected
  • <1.17.3-53.oe2203sp4
Fixed in
  • 1.17.3-53.oe2203sp4

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

AI-suggested

A fixed version 1.17.3-53.oe2203sp4 is available and should be applied to remediate these vulnerabilities. Users of affected golang versions should upgrade to this fixed release. No alternative mitigations or workarounds are indicated in the advisory. Since this is not a cloud service, remediation depends on user action to update the software.

Description

Multiple security vulnerabilities have been identified in the Go programming language (golang) affecting versions prior to 1.17.3-53.oe2203sp4. These include denial of service issues during certificate chain verification, memory exhaustion via HTTP/2 Trailer headers, bypass of HTTP/2 connection-level flow control limits, excessive CPU consumption from HTTP/2 SETTINGS frames, request smuggling risks with HTTP/1 CONNECT handling, and server crashes due to concurrent HPACK encoder modifications. These vulnerabilities have a critical severity rating and are addressed in the fixed version 1.17.3-53.oe2203sp4.

References

Community reviews

Loading reviews…