CVE-2025-61725: Excessive CPU consumption in ParseAddress in net/mail
Published Oct 29, 2025
·Updated
Excessive CPU consumption in ParseAddress in net/mail
Affected Software
15 affected componentsFixes available
Google Golang
Microsoft azl3 python-tensorboard 2.16.2-6
Microsoft cbl2 gcc 11.2.0-8
Microsoft cbl2 msft-golang 1.24.8-1
Microsoft azl3 golang 1.23.12-1
Microsoft cbl2 golang 1.18.8-10
Microsoft azl3 tensorflow 2.16.1-9
Microsoft cbl2 tensorflow 2.11.1-2
Microsoft cbl2 python-tensorboard 2.11.0-3
Microsoft azl3 golang 1.25.3-1
Microsoft azl3 gcc 13.2.0-7
Microsoft cbl2 golang 1.22.7-5
Microsoft azl3 golang 1.25.5-1
F5 BIG-IP Next for Kubernetes=2.1.0
2.2.0
IBM Concert Software<=1.0.0-2.2.0
Event History
Oct 29, 2025
CVE Published
via MITRE·10:10 PM
Data Sourced
via MITRE·10:10 PM
DescriptionWeakness
Data Sourced
via NVD·11:16 PM
DescriptionSeverity
Oct 31, 2025
Data Sourced
via Microsoft·01:05 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·01:05 AM
Affected Software
Updated
via Microsoft·01:05 AM
DescriptionSeverity
Updated
via Microsoft·01:05 AM
SeverityAffected Software
Feb 5, 2026
Advisory Published
via F5·05:15 PM
Data Sourced
via F5·05:15 PM
DescriptionSeverityWeaknessAffected Software
Apr 6, 2026
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2025-61725?
CVE-2025-61725 has been classified with a moderate severity due to its potential for excessive CPU consumption.
2
How do I fix CVE-2025-61725?
To fix CVE-2025-61725, update your version of Google Golang to the latest release that addresses the vulnerability.
3
What systems are affected by CVE-2025-61725?
CVE-2025-61725 affects implementations of Google Golang that utilize the ParseAddress function for domain-literal address components.
4
What are the potential impacts of CVE-2025-61725?
The potential impacts of CVE-2025-61725 include high CPU consumption which can degrade system performance and responsiveness.
5
Is CVE-2025-61725 being actively exploited?
As of now, there have been no known active exploits reported for CVE-2025-61725, but it is important to apply the fix to mitigate risks.