CVE-2026-84446

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

GHSA-xw34-mjcp-jqh8 ↗EUVD-2026-83017 ↗

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.23.1
fixed in 1.23.2
CWE-835 Loop with Unreachable Exit Condition ('Infinite Loop')
ETK-2026-523, permanent identifier
17d 07h 51msince last run
1h 18mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+371h14m
0
+2h
+4h
+6h
+8h
+10h

description

libheif before 1.23.2 can consume excessive CPU or memory or fail to finish processing a specially crafted HEIF sequence. An attacker must cause an application using the affected sequence-processing paths to open untrusted HEIF content.

mitigation

Upgrade libheif to version 1.23.2 or later. Until upgraded, restrict processing of untrusted HEIF sequence files, particularly where sequence or raw-sample APIs are enabled.

fixed in 1.23.2

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.
–
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.46%38th percentile
agent run time
1h 18m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-09-18 15:54Z
Δ 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

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-09-18 15:54Z
  2. 2026-09-18 15:54Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-523",
  "cve_id": "CVE-2026-84446",
  "display_id": "CVE-2026-84446",
  "ghsa_id": "GHSA-xw34-mjcp-jqh8",
  "euvd_id": "EUVD-2026-83017",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Resource exhaustion in libheif HEIF sequence handling",
  "summary": "libheif before 1.23.2 can consume excessive CPU or memory or fail to finish processing a specially crafted HEIF sequence. An attacker must cause an application using the affected sequence-processing paths to open untrusted HEIF content.",
  "mitigation": "Upgrade libheif to version 1.23.2 or later. Until upgraded, restrict processing of untrusted HEIF sequence files, particularly where sequence or raw-sample APIs are enabled.",
  "vendor": "strukturag",
  "product": "libheif",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "<= 1.23.1"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "1.23.2"
      ],
      "package_name": null,
      "purl": null
    }
  ],
  "cwes": [
    835
  ],
  "cvss_score": 7.5,
  "cvss_src": "nvd",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
  "epss_score": 0.0046,
  "epss_percentile": 0.3845,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 77.9520062,
  "t0_at": "2026-09-18T15:54:48.945000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-09-18T15:54:48.945000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-09-18T15:54:48.945000+00:00",
      "url": "https://github.com/strukturag/libheif/security/advisories/GHSA-xw34-mjcp-jqh8"
    }
  }
}

published 2026-10-04 01:50Z
last change 2026-10-21 10:52Z

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.