ETK-2026-2809Zero's internal tracking ID, independent of the CVE number.

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

GHSA-7qm8-hj35-269r ↗

no check availablenot proven exploitable
awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
other libheif >= 1.0.0, < 1.23.7
fixed in 1.23.7
CWE-834 Excessive Iteration
ETK-2026-2809Zero's internal tracking ID, independent of the CVE number., no cve assigned
2h 34msince last run
31mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal +0hwaiting for further signals+36h09m
0
+12h
+24h

description

libheif versions before 1.23.7 can consume excessive CPU while decoding specially formed HEIF images. An attacker who can supply a HEIF file to an application or service that uses libheif may tie up image-decoding workers.

mitigation

Upgrade libheif to version 1.23.7 or later. Until upgraded, restrict or isolate processing of untrusted HEIF files to reduce worker exhaustion risk.

fixed in 1.23.7

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
31m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
not published yet
Δ 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-26 11:53Z

this entry in the feed

GET /api/v1/feed/ETK-2026-2809

{
  "etk_id": "ETK-2026-2809",
  "cve_id": null,
  "display_id": "ETK-2026-2809",
  "ghsa_id": "GHSA-7qm8-hj35-269r",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "CPU exhaustion in libheif HEIF image decoding",
  "summary": "libheif versions before 1.23.7 can consume excessive CPU while decoding specially formed HEIF images. An attacker who can supply a HEIF file to an application or service that uses libheif may tie up image-decoding workers.",
  "mitigation": "Upgrade libheif to version 1.23.7 or later. Until upgraded, restrict or isolate processing of untrusted HEIF files to reduce worker exhaustion risk.",
  "vendor": "other",
  "product": "libheif",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 1.0.0, < 1.23.7"
      ],
      "ecosystem": "other",
      "fixed_versions": [
        "1.23.7"
      ],
      "package_name": "libheif",
      "purl": null
    }
  ],
  "cwes": [
    834
  ],
  "cvss_score": 7.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 31.468016416666668,
  "t0_at": null,
  "signals": {
    "trigger_signal": {
      "at": "2026-10-26T11:53:20+00:00",
      "days": -1.6126748802662036,
      "is_lower_bound": true,
      "measured_at": "2026-10-28T02:35:35.138017+00:00",
      "url": "https://github.com/strukturag/libheif/security/advisories/GHSA-7qm8-hj35-269r"
    }
  }
}

published 2026-10-28 00:08Z
last change 2026-10-28 02:23Z

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.