CVE-2026-103111

HIGHPre-NVD 7.67.6—
EchelonGraph scoreHIGH confidence

Score 7.6 from GitHub Security Advisory (severity: HIGH) published 2026-09-30. A secondary CVSS source baseline 7.6; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — Patch released this weekElevated
7.6EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.6Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
7.6
EG Score
7.6HIGHhigh confidence
EG Risk
50
EG Risk 50/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity76% × 45%
Exploitation40% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
9th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 30, 2026

Last Modified

October 4, 2026

Advisory Details (1)

Auto-updated Sep 30, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

PCRE2: out-of-bounds write in JIT matching with large stack allocations · Advisory · PCRE2Project/pcre2 · GitHub

Affected: 10.49

https://github.com/PCRE2Project/pcre2/security/advisories/GHSA-r9hj-j2rw-4q3m

Vendor Advisories for CVE-2026-103111(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatpcre2-main-10.49-0.1.hum12026-10-02redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 35× in last 7d / 35× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-04 12:16 UTCVendor advisory
  2. 2026-10-04 12:16 UTCGHSA enrichment
  3. 2026-10-04 00:20 UTCEG score recompute
  4. 2026-10-04 00:20 UTCVendor advisory
  5. 2026-10-04 00:20 UTCGHSA enrichment
  6. 2026-10-04 00:10 UTCEG score recompute
  7. 2026-10-04 00:10 UTCVendor advisory
  8. 2026-10-04 00:10 UTCGHSA enrichment
  9. 2026-10-03 20:08 UTCEG score recompute
  10. 2026-10-03 20:08 UTCVendor advisory
  11. 2026-10-03 20:07 UTCGHSA enrichment
  12. 2026-10-03 14:25 UTCEPSS rescore
  13. 2026-10-03 08:09 UTCVendor advisory
  14. 2026-10-03 08:09 UTCGHSA enrichment
  15. 2026-10-02 20:11 UTCEG score recompute
  16. 2026-10-02 20:11 UTCVendor advisory
  17. 2026-10-02 20:10 UTCGHSA enrichment
  18. 2026-10-02 08:13 UTCVendor advisory
  19. 2026-10-02 08:13 UTCGHSA enrichment
  20. 2026-10-01 20:17 UTCEG score recompute
  21. 2026-10-01 20:17 UTCVendor advisory
  22. 2026-10-01 20:16 UTCGHSA enrichment
  23. 2026-10-01 19:49 UTCEPSS rescore
  24. 2026-10-01 08:19 UTCVendor advisory
  25. 2026-10-01 08:19 UTCGHSA enrichment
Show 10 more
  1. 2026-09-30 20:23 UTCEG score recompute
  2. 2026-09-30 20:23 UTCGHSA enrichment
  3. 2026-09-30 19:26 UTCEG score recompute
  4. 2026-09-30 19:26 UTCGHSA enrichment
  5. 2026-09-30 17:25 UTCEG score recompute
  6. 2026-09-30 17:25 UTCGHSA enrichment
  7. 2026-09-30 15:02 UTCEPSS rescore
  8. 2026-09-30 05:34 UTCEG score recompute
  9. 2026-09-30 04:36 UTCEG score recompute
  10. 2026-09-30 04:34 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-103111?
CVE-2026-103111 is a high vulnerability published on September 30, 2026. 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.
When was CVE-2026-103111 disclosed?
CVE-2026-103111 was first published on September 30, 2026, with the most recent update on October 4, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-103111 actively exploited?
CVE-2026-103111 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (9th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-103111?
CVE-2026-103111 has a CVSS base score of 7.6 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-103111?
A fix for CVE-2026-103111 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-103111 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-103111

Explore →

Is Your Infrastructure Affected by CVE-2026-103111?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs