Enforce maximum recursion depth in encoding/asn1
Summary
| CVE | CVE-2026-33818 |
|---|---|
| State | PUBLISHED |
| Assigner | Go |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-08-13 22:17:19 UTC |
| Updated | 2026-08-14 16:16:55 UTC |
| Description | Enforce a recursion limit in Unmarshal to prevent stack exhaustion when parsing deeply-nested, recursive structures. |
Risk And Classification
Primary CVSS: v3.1 7.5 HIGH from ADP
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Problem Types: CWE-400 | CWE-400: Uncontrolled Resource Consumption | CWE-400 CWE-400 Uncontrolled Resource Consumption
| Version | Source | Type | Score | Severity | Vector |
|---|---|---|---|---|---|
| 3.1 | ADP | DECLARED | 7.5 | HIGH | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| 3.1 | 134c704f-9b21-4f2e-91b3-4a467353bcc0 | Secondary | 7.5 | HIGH | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
CVSS v3.1 Breakdown
Attack Vector
NetworkAttack Complexity
LowPrivileges Required
NoneUser Interaction
NoneScope
UnchangedConfidentiality
NoneIntegrity
NoneAvailability
HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Go Standard Library | Encoding/asn1 | affected 1.25.13 semver | Not specified |
| CNA | Go Standard Library | Encoding/asn1 | affected 1.26.0-0 1.26.6 semver | Not specified |
| CNA | Go Standard Library | Encoding/asn1 | affected 1.27.0-0 1.27.0-rc.3 semver | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| groups.google.com/g/golang-announce/c/94pEornpRlI | [email protected] | groups.google.com | |
| go.dev/issue/80405 | [email protected] | go.dev | |
| pkg.go.dev/vuln/GO-2026-5972 | [email protected] | pkg.go.dev | |
| go.dev/cl/814980 | [email protected] | go.dev | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
Vendor Comments And Credit
Discovery Credit
CNA: Marwan Atia ([email protected]) (en)
There are currently no legacy QID mappings associated with this CVE.