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

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

GHSA-hhg3-fxg7-3gxw ↗

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.21.0, < 1.23.7
fixed in 1.23.7
CWE-407 Inefficient Algorithmic Complexity
ETK-2026-2718Zero's internal tracking ID, independent of the CVE number., no cve assigned
3h 10msince last run
40mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal +0hwaiting for further signals+15h59m
0
+6h
+12h
+18h

description

libheif 1.21.0 through 1.23.6 can perform excessive CPU work while opening specially formed HEIF files. An attacker who can cause an application to process an untrusted HEIF file may tie up workers, including thumbnailing or decoding services.

mitigation

Upgrade libheif to version 1.23.7. Until upgrades are complete, restrict or isolate processing of untrusted HEIF files and apply resource limits to workers that handle them.

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
40m
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:51Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-2718",
  "cve_id": null,
  "display_id": "ETK-2026-2718",
  "ghsa_id": "GHSA-hhg3-fxg7-3gxw",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "CPU exhaustion from crafted HEIF files in libheif",
  "summary": "libheif 1.21.0 through 1.23.6 can perform excessive CPU work while opening specially formed HEIF files. An attacker who can cause an application to process an untrusted HEIF file may tie up workers, including thumbnailing or decoding services.",
  "mitigation": "Upgrade libheif to version 1.23.7. Until upgrades are complete, restrict or isolate processing of untrusted HEIF files and apply resource limits to workers that handle them.",
  "vendor": "other",
  "product": "libheif",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 1.21.0, < 1.23.7"
      ],
      "ecosystem": "other",
      "fixed_versions": [
        "1.23.7"
      ],
      "package_name": "libheif",
      "purl": null
    }
  ],
  "cwes": [
    407
  ],
  "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": 40.0446578,
  "t0_at": null,
  "signals": {
    "trigger_signal": {
      "at": "2026-10-26T11:51:56+00:00",
      "days": -0.7978176555092592,
      "is_lower_bound": true,
      "measured_at": "2026-10-27T07:00:47.490200+00:00",
      "url": "https://github.com/strukturag/libheif/security/advisories/GHSA-hhg3-fxg7-3gxw"
    }
  }
}

published 2026-10-27 03:32Z
last change 2026-10-27 06:57Z

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.