Cyber Resilience

CVE-2026-39836

Memory Safety in Golang Go ≤ 1.25.10

Memory Safety
Published
07 May 2026
Modified
17 June 2026
Patch / advisory
View advisory
CVSS Score v3.1 7.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.0059 45th percentile
Risk Priority 55 floored blend · peak EPSS

Summary

CVE-2026-39836 is a high-severity NULL Pointer Dereference (CWE-476) vulnerability in Golang Go. Its CVSS base score is 7.5 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Application or System Exploitation (T1499.004); ranked at the 45th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) and SI-2 (Flaw Remediation) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A10:2025 Mishandling of Exceptional Conditions

EU & UK References

Vulnerability Data

The Dial and LookupPort functions panic on Windows when provided with an input containing a NUL (0).

CWE(s)
CWE-476

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

T1499.004 Application or System Exploitation Impact
Adversaries may exploit software vulnerabilities that can cause an application or system to crash and deny availability to users.
attack.mitre.org →
Why these techniques?

NUL input to Dial/LookupPort directly triggers process panic/crash on Windows, enabling application DoS via exploitation.

Confidence: HIGH · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2026-33811Same product: Golang Go
CVE-2026-32283Same product: Golang Go
CVE-2026-32288Same product: Golang Go
CVE-2026-27137Same product: Golang Go
CVE-2025-61728Same product: Golang Go
CVE-2026-27138Same product: Golang Go
CVE-2026-32281Same product: Golang Go
CVE-2026-42499Same product: Golang Go
CVE-2026-25679Same product: Golang Go
CVE-2026-32280Same product: Golang Go

Affected Assets

golang
go
≤ 1.25.10 · 1.26.0 — 1.26.3

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • SI-10 Information Input Validation
  • SI-2 Flaw Remediation
Detect
Catch it (NIST detect / respond)
  • SI-4 System Monitoring
Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)

—

Mitigating Controls (NIST 800-53 r5) AI

SI-10 Information Input Validation good match
prevent

Validates and rejects NUL-containing inputs to Dial/LookupPort before they reach the vulnerable Windows code path, directly blocking the NULL dereference.

SI-2 Flaw Remediation good match
prevent

Requires prompt application of vendor patches that correct the NUL-handling flaw in the affected functions.

SI-4 System Monitoring partial match
detect

Monitors process crashes or unexpected terminations on Windows hosts that would result from triggering the panic.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices (static analysis, code review, safe coding standards) directly prevent NULL dereference bugs during development.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
detects

Security testing can detect NULL dereference defects before release.

A.8.25 Secure development life cycle partial match
prevents

Secure SDLC mandates defensive coding practices that can prevent NULL dereferences.

A.8.26 Application security requirements partial match
prevents

Application security requirements can specify input validation and pointer-safety rules.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles encourage defensive design that avoids unsafe pointer use.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly require NULL-pointer checks and safe dereference patterns.

References