CVE-2026-120208

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

GHSA-wqmc-6h9q-v6wp ↗EUVD-2026-114729 ↗

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.
strukturag libheif >= 1.18.0, < 1.23.3
fixed in 1.23.3
ETK-2026-3194Zero's internal tracking ID, independent of the CVE number., permanent identifier
5h 48msince last run
31mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+1h54m
0
+4h
+6h
+8h
+10h
+12h

description

strukturag libheif versions 1.18.0 through 1.23.2 are affected by a heap buffer overflow during HEIF image decoding. An attacker may cause out-of-bounds heap writes and potentially execute code if an application processes a crafted HEIF file with mismatched chroma-component bit depths.

mitigation

Upgrade strukturag libheif to version 1.23.3 or later. Until upgraded, restrict processing of untrusted HEIF files.

fixed in 1.23.3

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.
2026-10-31 17:25Z
Δ 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-31 17:25Z
    ghsa: trigger signal, started the run
  2. 2026-10-31 17:25Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-3194",
  "cve_id": "CVE-2026-120208",
  "display_id": "CVE-2026-120208",
  "ghsa_id": "GHSA-wqmc-6h9q-v6wp",
  "euvd_id": "EUVD-2026-114729",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Heap buffer overflow in strukturag libheif",
  "summary": "strukturag libheif versions 1.18.0 through 1.23.2 are affected by a heap buffer overflow during HEIF image decoding. An attacker may cause out-of-bounds heap writes and potentially execute code if an application processes a crafted HEIF file with mismatched chroma-component bit depths.",
  "mitigation": "Upgrade strukturag libheif to version 1.23.3 or later. Until upgraded, restrict processing of untrusted HEIF files.",
  "vendor": "strukturag",
  "product": "libheif",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 1.18.0, < 1.23.3"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "1.23.3"
      ],
      "package_name": "libheif",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 7.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 31.476546766666665,
  "t0_at": "2026-10-31T17:25:55.507000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-31T17:25:55.507000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-31T17:25:55.507000+00:00",
      "url": "https://github.com/advisories/GHSA-wqmc-6h9q-v6wp"
    }
  }
}

published 2026-10-31 18:48Z
last change 2026-11-01 00:11Z

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.