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

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

GHSA-35mc-3887-rr37 ↗

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.23.6
fixed in 1.23.7
CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
ETK-2026-2854Zero's internal tracking ID, independent of the CVE number., no cve assigned
3h 38msince last run
40mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal +0dwaiting for further signals+2.0d
0
+1d

description

libheif 1.23.6 is affected by a heap use-after-free race when decoding crafted HEIF images with derived tiles in parallel. An attacker who can cause an application or service to process an untrusted image may crash the image-processing worker or cause heap corruption; the affected path uses default parallel tile decoding.

mitigation

Upgrade libheif to version 1.23.7. Until upgrading, disable parallel tile decoding by setting the maximum decoding threads to 0.

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:54Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-2854",
  "cve_id": null,
  "display_id": "ETK-2026-2854",
  "ghsa_id": "GHSA-35mc-3887-rr37",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Heap use-after-free in libheif parallel tile decoding",
  "summary": "libheif 1.23.6 is affected by a heap use-after-free race when decoding crafted HEIF images with derived tiles in parallel. An attacker who can cause an application or service to process an untrusted image may crash the image-processing worker or cause heap corruption; the affected path uses default parallel tile decoding.",
  "mitigation": "Upgrade libheif to version 1.23.7. Until upgrading, disable parallel tile decoding by setting the maximum decoding threads to 0.",
  "vendor": "other",
  "product": "libheif",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "= 1.23.6"
      ],
      "ecosystem": "other",
      "fixed_versions": [
        "1.23.7"
      ],
      "package_name": "libheif",
      "purl": null
    }
  ],
  "cwes": [
    362
  ],
  "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": 39.81396013333333,
  "t0_at": null,
  "signals": {
    "trigger_signal": {
      "at": "2026-10-26T11:54:11+00:00",
      "days": -2.1077483130324075,
      "is_lower_bound": true,
      "measured_at": "2026-10-28T14:29:20.483280+00:00",
      "url": "https://github.com/strukturag/libheif/security/advisories/GHSA-35mc-3887-rr37"
    }
  }
}

published 2026-10-28 10:24Z
last change 2026-10-28 13: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.