CVE Program Container

Answer in brief

CVE-2026-86145 records a Unknown severity vulnerability in CVE Program Container. The current sources do not mark it as known exploited. The current feed maps PCRE/PCRE2 (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 5, 2026Updated Sep 5, 2026Source checked Sep 5, 2026First seen by HOL Sep 5, 2026Material review Sep 5, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps PCRE/PCRE2 (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
PCRE/PCRE2generic	>=10.32 <10.48	10.48

Recommended response

Check inventory. Check lockfiles and deployed manifests for PCRE/PCRE2.
Review the reported fix. Update PCRE/PCRE2 to 10.48 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 5, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 5, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 5, 2026

Sources and claim methodology

Upstream source description

PCRE2 before 10.48 allows a pcre2_dfa_match out-of-bounds write because reuse of a cached workspace block, in a recursive DFA matching workspace, lacks a size check (even though a newly allocated block, for the same purpose, does have a size check). This outcome requires an attacker-controlled regular expression, or a recursive pattern in conjunction with a small heap limit (this can be set through the API).

Quoted source text, attributed separately from HOL analysis.