CVE-2026-39820

HIGHNVD 7.57.5—Trending — 3 sources updated this week

7.5

Well-crafted inputs reaching ParseAddress, ParseAddressList, and ParseDate were able to trigger excessive CPU exhaustion and memory allocations.

CVSS v3: 7.5
EG Score: 7.5(high)
EPSS: 17.1%
KEV: Not listed

Published

May 7, 2026

Last Modified

May 13, 2026

References (4)

security@golanghttps://go.dev/cl/759940
security@golanghttps://go.dev/issue/78566
security@golanghttps://groups.google.com/g/golang-announce/c/qcCIEXso47M
security@golanghttps://pkg.go.dev/vuln/GO-2026-4986

Vendor Advisories for CVE-2026-39820(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

CVE-2026-39820
Microsoft Security Response Center (MSRC)High
Quadratic string concatentation in consumeComment in net/mail

Affected Packages

(1 across 1 ecosystem)

Go(1)

Package	Vulnerable range	Fixed in	Dependents
stdlib	—	1.26.3	—

Weakness Classification(1)

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

CWE-770Allocation of Resources Without Limits or Throttling

Data Freshness Timeline

(refreshed 20× in last 7d / 20× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-06-03 16:05 UTCEG score recompute
2026-06-03 16:05 UTCGHSA enrichment
2026-06-03 05:07 UTCEG score recompute
2026-06-03 05:07 UTCGHSA enrichment
2026-06-02 20:13 UTCepss_batch
2026-06-02 18:09 UTCEG score recompute
2026-06-02 18:09 UTCGHSA enrichment
2026-06-02 07:11 UTCEG score recompute
2026-06-02 07:11 UTCGHSA enrichment
2026-06-01 19:55 UTCEG score recompute
2026-06-01 19:55 UTCGHSA enrichment
2026-06-01 13:52 UTCepss_batch
2026-06-01 13:52 UTCepss_batch
2026-06-01 13:51 UTCepss_batch
2026-06-01 08:57 UTCEG score recompute
2026-06-01 08:57 UTCGHSA enrichment
2026-05-31 22:30 UTCepss_batch
2026-05-31 22:30 UTCepss_batch
2026-05-31 00:16 UTCepss_batch
2026-05-31 00:16 UTCepss_batch

Frequently asked(5)

What is CVE-2026-39820?

CVE-2026-39820 is a high vulnerability published on May 7, 2026. Well-crafted inputs reaching ParseAddress, ParseAddressList, and ParseDate were able to trigger excessive CPU exhaustion and memory allocations.

When was CVE-2026-39820 disclosed?

CVE-2026-39820 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-39820 actively exploited?

CVE-2026-39820 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 17.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2026-39820?

CVE-2026-39820 has a CVSS v3 base score of 7.5 (NVD).

How do I remediate CVE-2026-39820?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-39820, 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-39820

Explore →

Is Your Infrastructure Affected by CVE-2026-39820?

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

Start Free Scan →Browse All CVEs

CVE-2026-39820

📅 Published

🔄 Last Modified

🔗 References (4)

📣 Vendor Advisories for CVE-2026-39820(1)