Skip to content
Noroxi
CVE.org (no NVD analysis yet)· CNA mitre

CVE-2026-103111: PCRE2 before 10.49, when there is an attacker-controlled regular expression and certain JIT API usage, allows an out-of-bounds write with ar

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: 0.26% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: azl3 pcre2 10.48-1 on Azure Linux 3.0 Release Notes; azl3 rust 1.96.1-2 on Azure Linux 3.0 Release Notes.

Low priority for now. Upgrade to azl3 pcre2 10.48-1 on Azure Linux 3.0 Release Notes; azl3 rust 1.96.1-2 on Azure Linux 3.0 Release Notes 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

PCRE2 before 10.49, when there is an attacker-controlled regular expression and certain JIT API usage, allows an out-of-bounds write with arbitrary data.

HighCVSS 7.6 · v3.1—No exploit Fix available
Published
Sep 30, 2026
Updated
Oct 4, 2026
EPSS
0.2% · 19th percentile

Report tools

JSON

Action score

30

Monitor

Low priority for now.

CVSS
30 / 40 · 7.6 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
proof of concept
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · mitre
7.6
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

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.

Follow CVE-2026-103111

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for pcre records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

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 help

Affected 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.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (mitre). Independent of NVD's CPE analysis and usually ahead of it.

  • PCRE PCRE2

    • before 10.49affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10mariadb11.8before 3:11.8.8-2.el10_2.alma.23:11.8.8-2.el10_2.alma.2
AlmaLinux:10mariadb11.8-backupbefore 3:11.8.8-2.el10_2.alma.23:11.8.8-2.el10_2.alma.2
AlmaLinux:10mariadb11.8-client-utilsbefore 3:11.8.8-2.el10_2.alma.23:11.8.8-2.el10_2.alma.2
AlmaLinux:10mariadb11.8-commonbefore 3:11.8.8-2.el10_2.alma.23:11.8.8-2.el10_2.alma.2
AlmaLinux:10mariadb11.8-develbefore 3:11.8.8-2.el10_2.alma.23:11.8.8-2.el10_2.alma.2
AlmaLinux:10mariadb11.8-embeddedbefore 3:11.8.8-2.el10_2.alma.23:11.8.8-2.el10_2.alma.2
AlmaLinux:10mariadb11.8-embedded-develbefore 3:11.8.8-2.el10_2.alma.23:11.8.8-2.el10_2.alma.2
AlmaLinux:10mariadb11.8-errmsgbefore 3:11.8.8-2.el10_2.alma.23:11.8.8-2.el10_2.alma.2
AlmaLinux:10mariadb11.8-gssapi-serverbefore 3:11.8.8-2.el10_2.alma.23:11.8.8-2.el10_2.alma.2
AlmaLinux:10mariadb11.8-oqgraph-enginebefore 3:11.8.8-2.el10_2.alma.23:11.8.8-2.el10_2.alma.2
AlmaLinux:10mariadb11.8-pambefore 3:11.8.8-2.el10_2.alma.23:11.8.8-2.el10_2.alma.2
AlmaLinux:10mariadb11.8-serverbefore 3:11.8.8-2.el10_2.alma.23:11.8.8-2.el10_2.alma.2
AlmaLinux:10mariadb11.8-server-galerabefore 3:11.8.8-2.el10_2.alma.23:11.8.8-2.el10_2.alma.2
AlmaLinux:10mariadb11.8-server-utilsbefore 3:11.8.8-2.el10_2.alma.23:11.8.8-2.el10_2.alma.2
AlmaLinux:10mariadb11.8-testbefore 3:11.8.8-2.el10_2.alma.23:11.8.8-2.el10_2.alma.2
AlmaLinux:10pcre2before 10.44-1.5.el10_210.44-1.5.el10_2
AlmaLinux:10pcre2-develbefore 10.44-1.5.el10_210.44-1.5.el10_2
AlmaLinux:10pcre2-staticbefore 10.44-1.5.el10_210.44-1.5.el10_2
AlmaLinux:10pcre2-syntaxbefore 10.44-1.5.el10_210.44-1.5.el10_2
AlmaLinux:10pcre2-toolsbefore 10.44-1.5.el10_210.44-1.5.el10_2
AlmaLinux:10pcre2-utf16before 10.44-1.5.el10_210.44-1.5.el10_2
AlmaLinux:10pcre2-utf32before 10.44-1.5.el10_210.44-1.5.el10_2
AlmaLinux:8pcre2before 10.32-4.el8_1010.32-4.el8_10
AlmaLinux:8pcre2-develbefore 10.32-4.el8_1010.32-4.el8_10

+96

Same product

pcre: all records

Other 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 regular
    42Plan
  • 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 ot
    40Plan
  • 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 many
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-89160Sep 11, 2026 · PCRE2 before 10.48 has a pcre2_match out-of-bounds read during the PCRE2_MATCH_INVALID_UTF matching of an invalid UTF subject.
    26Monitor
  • ← EarlierCVE-2026-89161Sep 11, 2026 · In PCRE2 before 10.48, pcre2_jit_match mishandles a previously copied subject being passed in as a context.
    31Monitor
  • ← EarlierCVE-2026-89162Sep 11, 2026 · In PCRE2 before 10.48, pcre2_serialize_encode might disclose two bytes to an adversary, typically in a situation where the access available
    13Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
azl3 pcre2 10.48-1 on Azure Linux 3.0Release NotesMicrosoft (MSRC)
azl3 rust 1.96.1-2 on Azure Linux 3.0Release NotesMicrosoft (MSRC)
almalinux:mariadb11.83:11.8.8-2.el10_2.alma.2 · AlmaLinux:10Package registry (OSV)
almalinux:mariadb11.8-backup3:11.8.8-2.el10_2.alma.2 · AlmaLinux:10Package registry (OSV)
almalinux:mariadb11.8-client-utils3:11.8.8-2.el10_2.alma.2 · AlmaLinux:10Package registry (OSV)
almalinux:mariadb11.8-common3:11.8.8-2.el10_2.alma.2 · AlmaLinux:10Package registry (OSV)
almalinux:mariadb11.8-devel3:11.8.8-2.el10_2.alma.2 · AlmaLinux:10Package registry (OSV)
almalinux:pcre210.44-1.5.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:pcre2-devel10.44-1.5.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:pcre2-static10.44-1.5.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:pcre2-syntax10.44-1.5.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:pcre2-tools10.44-1.5.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:pcre2-utf1610.44-1.5.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:pcre2-utf3210.44-1.5.el10_2 · AlmaLinux:10Package registry (OSV)
alpine:pcre210.43-r1 · Alpine:v3.21Package registry (OSV)
alpine:pcre210.49-r0 · Alpine:v3.23Package registry (OSV)
debian:pcre210.42-1+deb12u2 · Debian:12Package registry (OSV)
debian:pcre210.46-1~deb13u3 · Debian:13Package registry (OSV)
opensuse:pcre210.49-2.1 · openSUSE:TumbleweedPackage registry (OSV)
red hat:pcre20:10.49-0.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:pcre2-debuginfo0:10.44-1.5.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:pcre2-debugsource0:10.44-1.5.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:pcre2-devel0:10.49-0.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:pcre2-static0:10.49-0.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:pcre2-syntax0:10.49-0.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:pcre2-tools0:10.49-0.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:pcre2-tools-debuginfo0:10.44-1.5.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:pcre2-utf160:10.49-0.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:pcre2-utf16-debuginfo0:10.44-1.5.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:pcre2-utf320:10.49-0.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)

+3

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.

  1. Published
  2. Fix recorded+1 d
  3. TodayOct 31, 2026+32 d
EPSS, last 120 days

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.

No commit or PR link among the references.

Credits

All researchers

Finders, 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.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
low · data can be read
Integrity
high · data or configuration can be modified
Availability
low · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
Low
Integrity impact
High
Availability impact
Low

Weakness class (CWE)

CWE-787 · Out-of-bounds Write

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:L

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓
  2. SSVC exploitation— → poc
  3. Exploit maturity— → none

For records you follow, these changes also arrive as notifications. →

References

Show all references (1 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records