Finding and attribution
In PCRE2 10.45, a regex combining (*scs:...) with (*ACCEPT) can leave end_subject and true_end_subject set to the end of the scanned substring when the assertion succeeds immediately. A later operation such as a backreference performs a bounds check using the shortened pointer; subtraction can underflow and allow memcmp to read beyond the subject buffer. An attacker-controlled regex pattern is required; crafted subject text alone cannot trigger the issue. PCRE2 10.44 and earlier are not affected. The maintainer says the issue could have denial-of-service or information-disclosure implications, but does not claim either was observed.
Product: PCRE2. AI system: Google Big Sleep. Team / organization: Google DeepMind / Google Project Zero.
CVE identifiers: CVE-2025-58050.
AI and human contribution (source account): The PCRE2 maintainer advisory embeds the original Google Big Sleep report and explicitly identifies the case by BIGSLEEP-438254142. Google Project Zero describes Big Sleep as a large-language-model-assisted vulnerability research agent developed with Google DeepMind and Project Zero. These sources establish system-level AI attribution for this exact issue; they do not state a specific model/version or private discovery date.
Human involvement is only described where the source account establishes it; unknown involvement does not mean none. Vendor confirmation of a flaw does not confirm every claim about AI contribution.
Discovery context: The maintainer advisory is the public disclosure; it does not establish whether defenders knew of the issue or whether it was exploited before disclosure.
Remediation status: fix documented. PCRE2 10.46, released 2025-08-27 as a security-only release, fixes the issue. The maintainer says only 10.45 is affected and 10.44 and earlier are unaffected. Release status does not establish downstream deployment.
A source-documented fix does not establish installed patches or current safety. Source checking does not independently reproduce the finding or establish observed exploitation.
Disclosed 27 Aug 2025. AI attribution dated 27 Aug 2025. Sources checked 16 Nov 2026; these are separate dates, not a live installation check.
Recorded CVSS: Medium · highest recorded score 6.9. Documented technical effects: denial of service, data disclosure.
Severity, consequences and exploitation evidence
Case grouping uses the highest recorded CVSS score, with its version-specific severity band. It is descriptive, not a combined or editorial risk index. All recorded assessments remain below; scores from different versions and sources may disagree. CVSS specifications define version-specific scoring and severity bands.
- CVE-2025-58050: CVSS 4.0 · 6.9 (Medium) ·
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:L/SC:L/SI:N/SA:L. PCRE2 GitHub Security Advisory (original Big Sleep report) · checked 16 Nov 2026.
CVE-2025-58050: denial of service, data disclosure.
Prerequisites / affected scope: Requires an attacker-controlled regex pattern combining (*scs:...) and (*ACCEPT), followed by an operation such as a backreference that uses the corrupted match boundary. Crafted subject text alone is insufficient. The maintainer says the read could have denial-of-service or information-disclosure implications; no observed downstream consequence is reported..
Exploitation evidence: The source documents an out-of-bounds read and a proof-of-concept/ASan report; it does not report exploitation in the wild.. Impact source · checked 16 Nov 2026.
Documented fix: PCRE2 10.46, released 2025-08-27 as a security-only release, fixes the issue. The maintainer says only 10.45 is affected and 10.44 and earlier are unaffected. Release status does not establish downstream deployment.