CVE-2026-102993

waiting for further signalsZero needs more public information before it can validate it.

GHSA-qv6h-rv94-w285 ↗EUVD-2026-90365 ↗

no check availablenot proven exploitable
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.
py-pdf pypdf < 6.17.0
fixed in 6.17.0
CWE-400 Uncontrolled Resource Consumption
ETK-2026-146, permanent identifier
pkg:pypi/pypdf
19d 14h 26msince last run
10mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+19h44m
0
+2h
+4h
+6h
+8h
+10h

description

pypdf versions before 6.17.0 can consume excessive memory while handling page labels in a crafted PDF. An attacker may make an application unavailable if it processes the document's page labels; exploitation requires the application to retrieve those labels.

mitigation

Upgrade pypdf to version 6.17.0 or later. Until upgrading, avoid retrieving page labels from untrusted PDFs and apply the upstream corrective change if feasible.

fixed in 6.17.0

check
no
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.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.35%27th percentile
agent run time
10m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-09-30 19:55Z
Δ 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

Contextual: an exploit technique exists, but no deterministic check could cover this one.

source signals

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

  1. 2026-09-30 19:55Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-146",
  "cve_id": "CVE-2026-102993",
  "display_id": "CVE-2026-102993",
  "ghsa_id": "GHSA-qv6h-rv94-w285",
  "euvd_id": "EUVD-2026-90365",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Memory exhaustion in pypdf Roman page-label processing",
  "summary": "pypdf versions before 6.17.0 can consume excessive memory while handling page labels in a crafted PDF. An attacker may make an application unavailable if it processes the document's page labels; exploitation requires the application to retrieve those labels.",
  "mitigation": "Upgrade pypdf to version 6.17.0 or later. Until upgrading, avoid retrieving page labels from untrusted PDFs and apply the upstream corrective change if feasible.",
  "vendor": "py-pdf",
  "product": "pypdf",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "< 6.17.0"
      ],
      "ecosystem": "pip",
      "fixed_versions": [
        "6.17.0"
      ],
      "package_name": "pypdf",
      "purl": "pkg:pypi/pypdf"
    }
  ],
  "cwes": [
    400
  ],
  "cvss_score": 8.7,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N",
  "epss_score": 0.0035,
  "epss_percentile": 0.2724,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 9.624554883333333,
  "t0_at": "2026-09-30T19:55:52.294000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-09-30T19:55:52.294000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-09-30T19:55:52.294000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-102993"
    }
  }
}

published 2026-09-30 20:27Z
last change 2026-10-21 06:02Z

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.