CVE-2026-109398

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

GHSA-3g9v-hjrx-mg5h ↗EUVD-2026-97495 ↗

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.
gumlet php-image-resize < 3.0.1
fixed in 3.0.1
CWE-409 Improper Handling of Highly Compressed Data (Data Amplification)
ETK-2026-1379Zero's internal tracking ID, independent of the CVE number., permanent identifier
8d 08h 57msince last run
11mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+4h35m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

php-image-resize versions earlier than 3.0.1 can use excessive PHP memory while processing compressed images that expand to very large decoded dimensions. An attacker who can submit an image for processing may cause a PHP worker to terminate.

mitigation

Upgrade php-image-resize to version 3.0.1 or later. Restrict untrusted image uploads until the upgrade is deployed.

fixed in 3.0.1

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.45%38th percentile
agent run time
11m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-12 15:16Z
Δ 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-10-12 15:16Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-1379",
  "cve_id": "CVE-2026-109398",
  "display_id": "CVE-2026-109398",
  "ghsa_id": "GHSA-3g9v-hjrx-mg5h",
  "euvd_id": "EUVD-2026-97495",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Memory-exhaustion denial of service in gumlet php-image-resize",
  "summary": "php-image-resize versions earlier than 3.0.1 can use excessive PHP memory while processing compressed images that expand to very large decoded dimensions. An attacker who can submit an image for processing may cause a PHP worker to terminate.",
  "mitigation": "Upgrade php-image-resize to version 3.0.1 or later. Restrict untrusted image uploads until the upgrade is deployed.",
  "vendor": "gumlet",
  "product": "php-image-resize",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 3.0.1"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "3.0.1"
      ],
      "package_name": "php-image-resize",
      "purl": null
    }
  ],
  "cwes": [
    409
  ],
  "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.0045,
  "epss_percentile": 0.3805,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 11.135587333333334,
  "t0_at": "2026-10-12T15:16:43.793000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-12T15:16:43.793000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-12T15:16:43.793000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-109398"
    }
  }
}

published 2026-10-12 16:12Z
last change 2026-10-21 04:45Z

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.