Integer overflow vulnerability in pcre2test before 10.41 allows attackers to cause a denial of service or other unspecified impacts via nega
Noroxi assessment
Priority: Monitor (action score 30/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.1% (FIRST EPSS); higher than 65.8% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: pcre2 (Alpine:v3.15) 10.42-r0; pcre2 (Alpine:v3.17) 10.41-r0; pcre2 (Debian:12) 10.42-1.
Low priority for now. Upgrade to pcre2 (Alpine:v3.15) 10.42-r0; pcre2 (Alpine:v3.17) 10.41-r0; pcre2 (Debian:12) 10.42-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Integer overflow vulnerability in pcre2test before 10.41 allows attackers to cause a denial of service or other unspecified impacts via negative input.
- Published
- Jul 18, 2023
- Updated
- Jun 17, 2026
- EPSS
- 1.1% · 65th percentile
- CWE
- CWE-190
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.1%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| pcre | pcre2 | cpe:2.3:a:pcre:pcre2 |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- pcre pcre2before 10.41
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.15 | pcre2 | before 10.42-r0 | 10.42-r0 |
| Alpine:v3.17 | pcre2 | before 10.41-r0 | 10.41-r0 |
| Debian:12 | pcre2 | before 10.42-1 | 10.42-1 |
| SUSE:Linux Enterprise Micro 5.3 | pcre2 | before 10.39-150400.4.9.1 | 10.39-150400.4.9.1 |
| SUSE:Linux Enterprise Micro 5.3 | pcre2 | before 10.39-150400.4.9.1 | 10.39-150400.4.9.1 |
| SUSE:Linux Enterprise Software Development Kit 12 SP5 | pcre2 | before 10.34-1.13.1 | 10.34-1.13.1 |
| SUSE:Manager Proxy 4.2 | pcre2 | before 10.31-150000.3.15.1 | 10.31-150000.3.15.1 |
Same product
pcre: all recordsOther highest-scoring records for the same primary product.
- CVE-2015-3210Heap-based buffer overflow in PCRE 8.34 through 8.37 and PCRE2 10.10 allows remote attackers to execute arbitrary code via a crafted regular42Plan
- CVE-2017-8786pcre2test.c in PCRE2 10.23 allows remote attackers to cause a denial of service (heap-based buffer overflow) or possibly have unspecified ot40Plan
- CVE-2017-8399PCRE2 before 10.30 has an out-of-bounds write caused by a stack-based buffer overflow in pcre2_match.c, related to a "pattern with very many40Plan
Published before and after this one in the same product
- ← EarlierCVE-2022-1586May 16, 2022 · An out-of-bounds read vulnerability was discovered in the PCRE2 library in the compile_xclass_matchingpath() function of the pcre2_jit_compi37Monitor
- ← EarlierCVE-2022-1587May 16, 2022 · An out-of-bounds read vulnerability was discovered in the PCRE2 library in the get_recurse_data_length() function of the pcre2_jit_compile.c37Monitor
- Later →CVE-2025-58050Aug 27, 2025 · PCRE2: heap-buffer-overflow read in match_ref due to missing boundary restoration in SCS27Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| alpine:pcre2 | 10.42-r0 · Alpine:v3.15 | Package registry (OSV) |
| debian:pcre2 | 10.42-1 · Debian:12 | Package registry (OSV) |
| opensuse:pcre2 | 10.39-150400.4.9.1 · openSUSE:Leap Micro 5.3 | Package registry (OSV) |
| suse:pcre2 | 10.31-150000.3.15.1 · SUSE:Manager Proxy 4.2 | Package registry (OSV) |
| suse:pcre2 | 10.39-150400.4.9.1 · SUSE:Linux Enterprise Micro 5.3 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-190 · Integer Overflow or WraparoundCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.