← Back
CVE-2026-33812
medium
CVSS 6.1
Excessive memory allocation when decoding malicious SFNT in golang.org/x/image
Summary
Excessive memory allocation when decoding malicious SFNT in golang.org/x/image
AI summary snake-internal / snake-template-v1
A weakness called CVE-2026-33812 was discovered in Excessive memory allocation.
Severity is Medium (CVSS 6.1/10). Exploitation requires specific conditions but can cause real harm if successful.
What you should do: update the affected software to the latest version. If unsure, ask your IT team or search the vendor's site for "Excessive memory allocation CVE-2026-33812".
CVE-2026-33812 (Excessive memory allocation). Severity: Medium / CVSSv3 6.1. Category: CWE-770.
Response plan:
1. Check the vendor advisory for affected versions and the patched release.
2. If a vulnerable version is running in production, schedule maintenance (urgency from KEV/CVSS).
3. If no patch yet, mitigate via WAF rule, disabling the affected feature, etc.
4. Monitor logs / SIEM for known IOC and PoC signatures of this CVE.
PoCs and fix commits: see the 'References' section, MITRE, and NVD.
❓ What is the problem
A weakness (CVE-2026-33812) in Excessive memory allocation. A serious software flaw has been identified.
📍 Affected scope
Target versions of Excessive memory allocation (see vendor advisory). If running in production, identify exposure immediately.
🔥 Severity
Severity: Medium (CVSS 6.1/10). Exploitation requires specific conditions but can cause real harm if successful.
🔧 How to fix
Update to the patched release as listed in the vendor advisory. (Typical mitigation pattern for CWE-770)
🛡️ Workaround
If a patch is not yet available, consider disabling the affected feature, applying WAF rules, blocking via network ACLs, or isolating the vulnerable version.
🔍 Detection
Check version information, scan dependencies via SBOM, and monitor SIEM for IOC and PoC signatures related to this CVE.
Affected packages
Go
golang.org/x/image
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.39.0"}]}]
References
- patch https://go.dev/cl/761180
- patch [email protected]
- report https://go.dev/issue/78382