CVE-2026-33818VulnerabilityPublished 19 Aug 2026Updated 10 Nov 2026

SUSE · Security update for go1.26

Affects SUSESource GCVE Database

Compare

Mentioned vulnerabilities

Authoritative record:CVE-2026-33818· High 7.5

Not known to be exploited · CVSS 7.5 High · fixed in SUSE package updates : patch SUSE asn1 soon.

Data as of 10 Nov 2026, 20:06 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CISA-ADP	CVSS 3.1	7.5

Patch: Available – fixed in 1.27.0-rc.3, 1.26.6, 1.25.13

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 13 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 10 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade encoding/asn1 to 1.27.0-rc.3, 1.26.6 or 1.25.13.

Affected software

Product	Affected	Fixed in
Go standard libraryencoding/asn1	Affected >=1.27.0-0 <1.27.0-rc.3	Fixed in 1.27.0-rc.3
Go standard libraryencoding/asn1	Affected >=1.26.0-0 <1.26.6	Fixed in 1.26.6
Go standard libraryencoding/asn1	Affected <1.25.13	Fixed in 1.25.13
Goencoding/asn1`pkg:golang/encoding/asn1`Other threats	Affected <1.25.13 >=1.26.0-0 <1.26.6 >=1.27.0-0 <1.27.0-rc.3	Fixed in 1.25.13 1.26.6 1.27.0-rc.3

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

Description

This update for go1.26 fixes the following issues: Update to go1.26.6 (released 2026-08-13, bsc#1255111). Security issues fixed: - CVE-2026-33818: encoding/asn1: unenforced recursion limit can lead to stack exhaustion when parsing deeply-nested, recursive structures (bsc#1275034). - CVE-2026-39821: golang.org/x/net/idna: failure to reject ASCII-only Punycode-encoded labels allows for validation bypass and privilege escalation (bsc#1266609). - CVE-2026-56853: net/http: missing timeout when doing unencrypted HTTP/2 check can lead to a denial of service (bsc#1275028). - CVE-2026-56858: html/template: improper Javascript regexp context tracking allows for XSS attacks (bsc#1275033). - CVE-2026-56859: encoding/xml: missing recursion depth guard during decode operation can lead to stack exhaustion and a denial of service (bsc#1275026). - CVE-2026-56860: net/url: quadratic time complexity in `resolvePath` when processing certain input can lead to high memory allocation overhead and a denial of service (bsc#1275029). - CVE-2026-56862: crypto/tls: no limit set for handshake messages sent post-handshake allows for denial of service (bsc#1275032). - CVE-2026-56864: x/mod/sumdb: unauthenticated hashes accepted in `Lookup` allows for a coordinating GOPROXY and GOSUMDB to serve a client malicious module content (bsc#1275025). - CVE-2026-56865: x/mod/sumdb/tlog: improper transparency log tile verification allows for bypass on crafted input and can lead to malicious module content to be accepted (bsc#1275024). Changes for go1.26.6: - go#79876 cmd/compile: prove misscompilation in slicemask folding leaves garbage in the upper bits - go#80099 cmd/compile: internal compiler error invalid heap allocated var without Heapaddr - go#80131 cmd/link: peCreateExportFile generates invalid .def file when output name has trailing dot (c-shared on Windows) - go#80365 os: Root's MkdirAll can't create paths ending in forward slashes - go#80367 os: TestRootMultiReadFile fails on netbsd/arm64 after CL 797880 - go#80369 os: TestRootConsistencyRemoveAll fails on Plan 9 after CL 797880 - go#80394 runtime: arm64 found pointer to free object with safe code - go#80441 runtime: uninitialized register due to wrong ABI in mach_vm_region_trampoline leads to libc following garbage stack data as a pointer - go#80478 cmd/compile: riscv64 miscompiles struct copy, corrupting a []byte slice field - go#80499 runtime: js/wasm: "found bad pointer in Go heap" -- link-layout-constant value recorded as a pointer in the write-barrier buffer - go#80579 cmd/compile: regalloc uses unreliable type data (like v.Type.IsSigned()) to choose the restore of spills - go#80606 crypto/tls: escape hatch for FIPS 140-3 mode Extended Master Secret enforcement - go#80609 net, x/net/dns/dnsmessage: panic when parsing invalid SVCB record - go#80615 cmd/compile: mips64le misscompile OffPtr by a const which doesn't fit 32bits resulting in panic - go#80617 cmd/compile: mips/mips64, multiply/divide results spilled from HI/LO corrupted w/ big stack frames - go#80619 cmd/compile: prove bug causes invalid indirect call - go#80715 runtime: fpTracebackPartialExpand SIGSEGV under high panic load

References

Community reviews

Loading reviews…