Out-of-Bounds Write in PCRE2 (CVE-2026-103111)
Summary
Out-of-bounds write in PCRE2 (CVE-2026-103111). Data can be tampered with by attackers.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-103111 has been found in PCRE2.
Data can be tampered with by attackers. CVSS score: 7.6/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "PCRE2 CVE-2026-103111" on the vendor's site.
CVE-2026-103111 (PCRE2) — CWE-787 / CVSS v3 7.6
Attack vector: remote (network-reachable) / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Out-of-bounds write (CWE-787) exists in PCRE2.
Check the vendor advisory for the affected versions of PCRE2.
Severity: High (CVSS 7.6/10). Data can be tampered with by attackers.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'PCRE2' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'PCRE2' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
PCRE2を grep し、稼働しているサービス・バージョンを把握する。 -
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web github.com
- web lists.debian.org
- web nvd.nist.gov
- web github.com