CPU exhaustion via repeated invalid-block rescanning
Published Oct 29, 2025 · Updated Oct 29, 2025
Algorithmic complexity in Go encoding/pem before 1.24.8 and 1.25.0 through 1.25.1 allows remote attackers to exhaust CPU. Decode searches for a BEGIN marker before an END marker, then rescans the remaining input after each invalid block, producing quadratic work. A reachable program must pass attacker-controlled PEM data with many BEGIN lines and one terminal END line; the bounded consequence is CPU exhaustion and service interruption.
Summary
What happened
Algorithmic complexity in Go encoding/pem before 1.24.8 and 1.25.0 through 1.25.1 allows remote attackers to exhaust CPU. Decode searches for a BEGIN marker before an END marker, then rescans the remaining input after each invalid block, producing quadratic work. A reachable program must pass attacker-controlled PEM data with many BEGIN lines and one terminal END line; the bounded consequence is CPU exhaustion and service interruption.
The record
- CVE
- CVE-2025-61723
- Published
- Oct 29, 2025
- Updated
- Oct 29, 2025
- Vendor
- Go
- Product
- encoding/pem
- Classifications
- CWE-770, CWE-407, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 29, 2025CVE publishedPublication date reported by the CVE source.
- Oct 29, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <1.24.8
- Affected versionversion=1.25.0 <1.25.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo