Vulnerabilities

Vulnerability · 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 arbitrary data.

Published Sep 30, 2026 · catalog updated Oct 21, 2026 · PCRE2 before 10.49, when

Open the advisory

Exploitation likelihood is not on this record for CVE-2026-103111. A missing EPSS score is not a low risk. Compare PCRE2 before 10.49, when with the linked advisory before you change production.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (PCRE2 before 10.49, when).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
  • EPSS is missing. A missing score is not a low risk.
Severity
High7.6
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
Awaiting synchronization with FIRST
Remediation
Advisory link
Affected products
Alpine:v3.21 pcre2 · Alpine:v3.22 pcre2 · Alpine:v3.23 pcre2 · Alpine:v3.24 pcre2

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.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • Alpine:v3.21 pcre20 → 10.43-r1
  • Alpine:v3.22 pcre20 → 10.46-r1
  • Alpine:v3.23 pcre20 → 10.49-r0
  • Alpine:v3.24 pcre20 → 10.49-r0

How to fix CVE-2026-103111

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

Exploitation likelihood is not on this record for CVE-2026-103111. A missing EPSS score is not a low risk. Compare PCRE2 before 10.49, when with the linked advisory before you change production.

Which versions are affected?

Compare what you have installed with 0 → 10.43-r1, 0 → 10.46-r1, 0 → 10.49-r0. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS is not on this record yet. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Sep 30, 2026 · Trivy Vulnerability DB

    Detected

    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.

  2. Oct 21, 2026 · Trivy Vulnerability DB

    Fix available

    pcre2 fixed in 10.43-r1; pcre2 fixed in 10.46-r1; pcre2 fixed in 10.49-r0; pcre2 fixed in 10.49-r0

  3. Oct 21, 2026 · Trivy Vulnerability DB

    Fix available

    pcre2 fixed in 10.43-r1

  4. Oct 21, 2026 · Trivy Vulnerability DB

    Fix available

    pcre2 fixed in 10.46-r1

  5. Oct 21, 2026 · Trivy Vulnerability DB

    Fix available

    pcre2 fixed in 10.49-r0

  6. Oct 21, 2026 · Trivy Vulnerability DB

    Updated

    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.

Sources

  • CVE.orgVulnerability recordCVE-2026-103111

    Official CVE identifier

    cve.org
  • Trivy Vulnerability DBPackage advisoryALPINE-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 arbitrary data.

    osv.dev

References

Freshness

Last verified in this catalog Oct 21, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.