CVE-2026-42499 | Quadratic string concatenation in consumePhrase in net/mail

Pathological inputs could cause DoS through consumePhrase when parsing an email address according to RFC 5322.

Published: 2026-05-07 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2026-42499 is rated Moderate Risk (45.5/100): CVSS High severity, with low exploitation likelihood (EPSS 0.58%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2026-42499

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.01% 0.58% +0.57%
2 2026-05-08 — 0.01% —

Full EPSS history (2 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-42499

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 3.6 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2026-42499

GitHub Security Advisory for CVE-2026-42499

GHSA-xq5j-9r39-c3vf · Severity: high — Pathological inputs could cause DoS through consumePhrase when parsing an email address according...

OS Trackers for CVE-2026-42499

vendor priority summary link
debian not yet assigned CVE-2026-42499 not yet assigned priority: Debian including 5 source packages (golang-1.15, golang-1.19, golang-1.24, golang-1.25, golang-1.26), 7 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 4, open 3. https://security-tracker.debian.org/tracker/CVE-2026-42499
suse high CVE-2026-42499 severity important: SUSE including 13 source package names (go, go-doc, …), 105 product×package rows across 17 product lines (SUSE Linux Enterprise High Performance Computing 15 SP4-ESPOS, SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS, … (17 product lines)): First Fixed 72, Known Not Affected 29, Fixed 4. https://www.suse.com/security/cve/CVE-2026-42499/
ubuntu medium CVE-2026-42499 medium priority: Ubuntu including 16 source packages (golang, golang-1.10, …), 98 status rows across 9 suites (bionic, focal, jammy, noble, questing, resolute, trusty, upstream, xenial): needs-triage 52, DNE 46. https://ubuntu.com/security/CVE-2026-42499

Affected software / configurations for CVE-2026-42499

Vendor Product Version Raw CPE
golang go < 1.25.10 cpe:2.3:a:golang:go:*:*:*:*:*:*:*:*
golang go >= 1.26.0, < 1.26.3 cpe:2.3:a:golang:go:*:*:*:*:*:*:*:*

References for CVE-2026-42499

cvelogic Threat Intelligence