CVE-2026-39836

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-05-07. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

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

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
46%
KEV
Not listed

Published

May 7, 2026

Last Modified

May 13, 2026

Advisory Details (4)

Auto-updated Jun 5, 2026
No patch confirmed yet.
generic

GO-2026-4971 - Go Packages

https://pkg.go.dev/vuln/GO-2026-4971
generic

net: panic in Dial and LookupPort when handling NUL byte on Windows (fix CVE-2026-39836) · Issue #79006 · golang/go · GitHub

https://go.dev/issue/79006

Patch Availability(10)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
stdlib1.26.3

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 80× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 207 total refreshes for this CVE.

  1. 2026-08-25 13:49 UTCEPSS rescore
  2. 2026-08-23 19:33 UTCEG score recompute
  3. 2026-08-23 19:33 UTCVendor advisory
  4. 2026-08-23 19:33 UTCGHSA enrichment
  5. 2026-08-23 00:19 UTCEPSS rescore
  6. 2026-08-21 23:49 UTCEPSS rescore
  7. 2026-08-20 22:55 UTCEPSS rescore
  8. 2026-08-19 17:03 UTCEPSS rescore
  9. 2026-08-18 13:48 UTCEPSS rescore
  10. 2026-08-17 13:47 UTCEPSS rescore
  11. 2026-08-17 12:43 UTCEG score recompute
  12. 2026-08-17 12:43 UTCVendor advisory
  13. 2026-08-17 12:43 UTCGHSA enrichment
  14. 2026-08-16 14:56 UTCEPSS rescore
  15. 2026-08-16 04:42 UTCEG score recompute
  16. 2026-08-16 04:42 UTCVendor advisory
  17. 2026-08-16 04:42 UTCGHSA enrichment
  18. 2026-08-16 02:14 UTCEPSS rescore
  19. 2026-08-15 01:30 UTCEPSS rescore
  20. 2026-08-14 15:41 UTCVendor advisory
  21. 2026-08-14 15:41 UTCGHSA enrichment
  22. 2026-08-14 03:18 UTCEG score recompute
  23. 2026-08-14 03:18 UTCVendor advisory
  24. 2026-08-14 03:18 UTCGHSA enrichment
  25. 2026-08-13 22:00 UTCEPSS rescore
Show 75 more
  1. 2026-08-13 06:01 UTCVendor advisory
  2. 2026-08-13 06:01 UTCGHSA enrichment
  3. 2026-08-12 16:52 UTCEG score recompute
  4. 2026-08-12 16:52 UTCVendor advisory
  5. 2026-08-12 16:52 UTCGHSA enrichment
  6. 2026-08-12 13:51 UTCEPSS rescore
  7. 2026-08-11 15:55 UTCEG score recompute
  8. 2026-08-11 15:55 UTCVendor advisory
  9. 2026-08-11 15:54 UTCGHSA enrichment
  10. 2026-08-11 13:43 UTCEPSS rescore
  11. 2026-08-11 01:24 UTCEG score recompute
  12. 2026-08-11 01:24 UTCVendor advisory
  13. 2026-08-11 01:24 UTCGHSA enrichment
  14. 2026-08-11 00:00 UTCEPSS rescore
  15. 2026-08-10 03:14 UTCVendor advisory
  16. 2026-08-10 03:14 UTCGHSA enrichment
  17. 2026-08-09 14:51 UTCEG score recompute
  18. 2026-08-09 14:51 UTCVendor advisory
  19. 2026-08-09 14:51 UTCGHSA enrichment
  20. 2026-08-09 13:46 UTCEPSS rescore
  21. 2026-08-09 02:28 UTCEG score recompute
  22. 2026-08-09 02:28 UTCVendor advisory
  23. 2026-08-09 02:28 UTCGHSA enrichment
  24. 2026-08-08 16:37 UTCEPSS rescore
  25. 2026-08-08 02:34 UTCEG score recompute
  26. 2026-08-08 02:34 UTCVendor advisory
  27. 2026-08-08 02:34 UTCGHSA enrichment
  28. 2026-08-07 14:10 UTCVendor advisory
  29. 2026-08-07 14:10 UTCGHSA enrichment
  30. 2026-08-07 01:48 UTCEG score recompute
  31. 2026-08-07 01:48 UTCVendor advisory
  32. 2026-08-07 01:48 UTCGHSA enrichment
  33. 2026-08-06 13:46 UTCEPSS rescore
  34. 2026-08-06 10:45 UTCVendor advisory
  35. 2026-08-06 10:45 UTCGHSA enrichment
  36. 2026-08-05 22:13 UTCEG score recompute
  37. 2026-08-05 22:13 UTCVendor advisory
  38. 2026-08-05 22:13 UTCGHSA enrichment
  39. 2026-08-05 19:17 UTCEPSS rescore
  40. 2026-08-04 15:10 UTCEPSS rescore
  41. 2026-08-04 10:38 UTCEPSS rescore
  42. 2026-08-03 19:36 UTCEG score recompute
  43. 2026-08-03 19:36 UTCVendor advisory
  44. 2026-08-03 19:36 UTCGHSA enrichment
  45. 2026-08-03 10:36 UTCEPSS rescore
  46. 2026-08-02 16:53 UTCVendor advisory
  47. 2026-08-02 16:53 UTCGHSA enrichment
  48. 2026-08-02 04:30 UTCEG score recompute
  49. 2026-08-02 04:30 UTCVendor advisory
  50. 2026-08-02 04:30 UTCGHSA enrichment
  51. 2026-08-02 02:27 UTCEPSS rescore
  52. 2026-08-01 04:16 UTCEPSS rescore
  53. 2026-07-30 16:28 UTCEPSS rescore
  54. 2026-07-30 01:30 UTCEPSS rescore
  55. 2026-07-27 14:13 UTCEPSS rescore
  56. 2026-07-26 14:54 UTCEPSS rescore
  57. 2026-07-26 14:54 UTCEPSS rescore
  58. 2026-07-25 14:18 UTCEPSS rescore
  59. 2026-07-25 14:18 UTCEPSS rescore
  60. 2026-07-24 14:17 UTCEPSS rescore
  61. 2026-07-24 14:17 UTCEPSS rescore
  62. 2026-07-23 14:18 UTCEPSS rescore
  63. 2026-07-23 14:18 UTCEPSS rescore
  64. 2026-07-23 03:10 UTCEG score recompute
  65. 2026-07-22 14:08 UTCEPSS rescore
  66. 2026-07-21 15:24 UTCEPSS rescore
  67. 2026-07-20 17:08 UTCEPSS rescore
  68. 2026-07-19 14:31 UTCEPSS rescore
  69. 2026-07-19 02:29 UTCEPSS rescore
  70. 2026-07-18 10:04 UTCEPSS rescore
  71. 2026-07-16 17:03 UTCEPSS rescore
  72. 2026-07-16 09:53 UTCOSV refresh
  73. 2026-07-15 16:57 UTCEPSS rescore
  74. 2026-07-15 16:57 UTCEPSS rescore
  75. 2026-07-15 02:00 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-39836?
CVE-2026-39836 is a high vulnerability published on May 7, 2026. The Dial and LookupPort functions panic on Windows when provided with an input containing a NUL (0).
When was CVE-2026-39836 disclosed?
CVE-2026-39836 was first published in the National Vulnerability Database on May 7, 2026, with the most recent update on May 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-39836 actively exploited?
CVE-2026-39836 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 54.5% of all scored CVEs.
What is the CVSS score of CVE-2026-39836?
CVE-2026-39836 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-39836?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-39836, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-39836

Explore →

Is Your Infrastructure Affected by CVE-2026-39836?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.