Skip to content

net/mail: excessive CPU consumption in ParseAddress (CVE-2025-61725) #75680

Closed

Description

@neild

The ParseAddress function constructed domain-literal address components through repeated string concatenation. When parsing large domain-literal components, this could cause excessive CPU consumption.

Thanks to Philippe Antoine (Catena cyber) for reporting this issue.

This is CVE-2025-61725 and Go issue https://go.dev/issue/75680.


This is a PRIVATE issue for CVE-2025-61725, tracked in http://b/446728192 and fixed by https://go-internal-review.git.corp.google.com/c/go/+/2840.

/cc @golang/security and @golang/release

Activity

  1. added this to the Go1.26 milestone on Sep 30, 2025
  2. neild commented on Oct 1, 2025

    @neild
    ContributorAuthor

    @gopherbot please open backport issues for this security fix

  3. gopherbot commented on Oct 1, 2025

    @gopherbot
    Contributor

    Backport issue(s) opened: #75700 (for 1.24), #75701 (for 1.25).

    Remember to create the cherry-pick CL(s) as soon as the patch is submitted to master, according to https://go.dev/wiki/MinorReleases.

  4. added
    NeedsFixThe path to resolution is known, but the work has not been done.
    on Oct 2, 2025
  5. gopherbot commented on Oct 7, 2025

    @gopherbot
    Contributor

    Change https://go.dev/cl/709835 mentions this issue: [release-branch.go1.24] net/mail: avoid quadratic behavior in mail address parsing

  6. gopherbot commented on Oct 7, 2025

    @gopherbot
    Contributor

    Change https://go.dev/cl/709860 mentions this issue: net/mail: avoid quadratic behavior in mail address parsing

  7. gopherbot commented on Oct 7, 2025

    @gopherbot
    Contributor

    Change https://go.dev/cl/709844 mentions this issue: [release-branch.go1.25] net/mail: avoid quadratic behavior in mail address parsing

  8. changed the title [-]security: fix CVE-2025-61725[/-] [+]net/mail: excessive CPU consumption in ParseAddress (CVE-2025-61725)[/+] on Oct 7, 2025
  9. locked and limited conversation to collaborators on Oct 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions