CVE-2026-119204

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

GHSA-cggf-277g-3q54 ↗EUVD-2026-113375 ↗

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.21.4
fixed in >= 6.21.4
CWE-400 Uncontrolled Resource Consumption
ETK-2026-3015Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:pypi/pypi
6h 15msince last run
11mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+2h39m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

pypdf versions earlier than 6.21.4 can use disproportionate memory when parsing certain PDF page-tree structures. An attacker who can cause an application to process a crafted PDF may exhaust available memory and disrupt that application.

mitigation

Upgrade pypdf to version 6.21.4 or later. Until upgrading, restrict processing of untrusted PDFs and apply resource limits to PDF-processing workloads.

fixed in >= 6.21.4

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.
–
agent run time
11m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-29 20:34Z
Δ 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, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

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

  1. 2026-10-29 20:34Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-3015",
  "cve_id": "CVE-2026-119204",
  "display_id": "CVE-2026-119204",
  "ghsa_id": "GHSA-cggf-277g-3q54",
  "euvd_id": "EUVD-2026-113375",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Memory exhaustion in pypdf PDF page-tree parsing",
  "summary": "pypdf versions earlier than 6.21.4 can use disproportionate memory when parsing certain PDF page-tree structures. An attacker who can cause an application to process a crafted PDF may exhaust available memory and disrupt that application.",
  "mitigation": "Upgrade pypdf to version 6.21.4 or later. Until upgrading, restrict processing of untrusted PDFs and apply resource limits to PDF-processing workloads.",
  "vendor": "py-pdf",
  "product": "pypdf",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "< 6.21.4"
      ],
      "ecosystem": "pip",
      "fixed_versions": [
        ">= 6.21.4"
      ],
      "package_name": "pypi",
      "purl": "pkg:pypi/pypi"
    }
  ],
  "cwes": [
    400
  ],
  "cvss_score": 7.1,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 11.368355966666666,
  "t0_at": "2026-10-29T20:34:02.704000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-29T20:34:02.704000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-29T20:34:02.704000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-119204"
    }
  }
}

published 2026-10-29 23:01Z
last change 2026-10-30 05:07Z

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.