Approved changes feed: RSS · Atom
cpe:2.3:a:go_standard_library:net/mail:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Go Standard Library (50bc78d3-15d0-59a4-bc22-a964570e0614) |
|---|---|
| Product | Net/Mail (c8fda7c8-5e7a-57aa-b4da-7ca0a8a1f073) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-42499 |
vulnerable | 2026-06-08 08:03:16.367291 |
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-07T19:41:18.615Z
Updated: 2026-07-31T12:04:47.585Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-39820 |
vulnerable | 2026-06-08 08:01:17.056659 |
Quadratic string concatentation in consumeComment in net/mail
Well-crafted inputs reaching ParseAddress, ParseAddressList, and ParseDate were able to trigger excessive CPU exhaustion and memory allocations.
Published: 2026-05-07T19:41:19.854Z
Updated: 2026-07-31T12:04:40.820Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-61725 |
vulnerable | 2026-06-08 07:37:27.955944 |
Excessive CPU consumption in ParseAddress in net/mail
The ParseAddress function constructs domain-literal address components through repeated string concatenation. When parsing large domain-literal components, this can cause excessive CPU consumption.
Published: 2025-10-29T22:10:12.255Z
Updated: 2025-12-09T17:42:06.541Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-24784 |
vulnerable | 2026-06-08 06:29:41.750116 |
Comments in display names are incorrectly handled in net/mail
The ParseAddressList function incorrectly handles comments (text within parentheses) within display names. Since this is a misalignment with conforming address parsers, it can result in different trust decisions being made by programs using different parsers.
Published: 2024-03-05T22:22:32.186Z
Updated: 2025-02-13T17:40:24.430Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.