Memory disclosure via stale substring boundary
Published Aug 27, 2025 · Updated Aug 27, 2025
A heap-buffer-overflow read in PCRE2 10.45's matching engine allows remote attackers to disclose memory via a crafted regex pattern. An immediate (*ACCEPT) inside (*scs:...) leaves end_subject shortened, so unsigned bounds arithmetic lets match_ref pass and memcmp read beyond the heap allocation. Exploitation requires control of the regular expression pattern; crafted subject text alone cannot trigger the flaw, and consequences are bounded to information disclosure or a process crash.
Summary
What happened
A heap-buffer-overflow read in PCRE2 10.45's matching engine allows remote attackers to disclose memory via a crafted regex pattern. An immediate (*ACCEPT) inside (*scs:...) leaves end_subject shortened, so unsigned bounds arithmetic lets match_ref pass and memcmp read beyond the heap allocation. Exploitation requires control of the regular expression pattern; crafted subject text alone cannot trigger the flaw, and consequences are bounded to information disclosure or a process crash.
The record
- CVE
- CVE-2025-58050
- Published
- Aug 27, 2025
- Updated
- Aug 27, 2025
- Vendor
- PCRE2 Project
- Product
- PCRE2
- Classifications
- CWE-122, CWE-125
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 27, 2025CVE publishedPublication date reported by the CVE source.
- Aug 27, 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== 10.45
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.
Public exploit references
- Upstream AddressSanitizer reproducerproof of concept · demonstrated
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