CVE-2026-103111

validatedZero produced an exploit or a check.

GHSA-mq4r-p73m-gphj ↗EUVD-2026-89608 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
PCRE PCRE2 <=10.48
fixed in 10.49
CWE-787 Out-of-bounds Write
ETK-2026-80, permanent identifier
+1h25mTTV
24mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = cve.org publication
trigger signal (cve.org) +0mcheck available+85magent stopped
0
+30min
+60min
+90min

description

PCRE2 versions before 10.49 are affected by an out-of-bounds write during certain JIT API operations. An attacker may trigger the flaw with a controlled regular expression where an application processes untrusted patterns through the affected JIT path.

mitigation

Upgrade PCRE2 to version 10.49 or later. Until upgraded, avoid compiling or executing untrusted regular expressions with the affected JIT API usage.

fixed in 10.49

check
available
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.21%11th percentile
agent run time
24m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-09-30 04:13Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Mechanism verified: the exploit fired on the vulnerable build and stayed silent on the patched one, but the server it ran against was ours, so no check ships for it.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-09-30 04:13Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-103111

{
  "etk_id": "ETK-2026-80",
  "cve_id": "CVE-2026-103111",
  "display_id": "CVE-2026-103111",
  "ghsa_id": "GHSA-mq4r-p73m-gphj",
  "euvd_id": "EUVD-2026-89608",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Out-of-bounds write in PCRE2 JIT processing",
  "summary": "PCRE2 versions before 10.49 are affected by an out-of-bounds write during certain JIT API operations. An attacker may trigger the flaw with a controlled regular expression where an application processes untrusted patterns through the affected JIT path.",
  "mitigation": "Upgrade PCRE2 to version 10.49 or later. Until upgraded, avoid compiling or executing untrusted regular expressions with the affected JIT API usage.",
  "vendor": "PCRE",
  "product": "PCRE2",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "<=10.48"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "10.49"
      ],
      "package_name": "PCRE2",
      "purl": null
    }
  ],
  "cwes": [
    787
  ],
  "cvss_score": 7.6,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:L",
  "epss_score": 0.0021,
  "epss_percentile": 0.1112,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "mechanism_verified",
  "exploit": false,
  "pipeline_minutes": 24.451215166666667,
  "t0_at": "2026-09-30T04:13:59.115000+00:00",
  "signals": {
    "check": {
      "at": "2026-09-30T05:38:59.304230+00:00",
      "days": 0.05902996793981481,
      "is_lower_bound": false,
      "measured_at": "2026-09-30T04:13:59.115000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-09-30T04:13:59.115000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-09-30T04:13:59.115000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-103111"
    }
  }
}

published 2026-09-30 05:14Z
last change 2026-10-21 06:34Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.