CVE-2026-84444

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

GHSA-j264-xvrp-5v7q ↗EUVD-2026-83020 ↗

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-787 Out-of-bounds Write
ETK-2026-177, permanent identifier
20d 04h 40msince last run
28mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+297h07m
0
+2h
+4h
+6h
+8h
+10h

description

libheif versions before 1.23.2 can write beyond a heap buffer while adding tiles to uncompressed tiled images. An attacker or caller able to submit mismatched component-plane dimensions through the tile API may trigger the flaw when the uncompressed codec is enabled.

mitigation

Upgrade libheif to version 1.23.2 or later. Disable the uncompressed codec where it is not required until upgrades are complete.

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.48%39th percentile
agent run time
28m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-09-18 15:56Z
Δ 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:56Z
  2. 2026-09-18 15:56Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-177",
  "cve_id": "CVE-2026-84444",
  "display_id": "CVE-2026-84444",
  "ghsa_id": "GHSA-j264-xvrp-5v7q",
  "euvd_id": "EUVD-2026-83020",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Heap overflow in libheif uncompressed tiled-image encoding",
  "summary": "libheif versions before 1.23.2 can write beyond a heap buffer while adding tiles to uncompressed tiled images. An attacker or caller able to submit mismatched component-plane dimensions through the tile API may trigger the flaw when the uncompressed codec is enabled.",
  "mitigation": "Upgrade libheif to version 1.23.2 or later. Disable the uncompressed codec where it is not required until upgrades are complete.",
  "vendor": "strukturag",
  "product": "libheif",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "<= 1.23.1"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "1.23.2"
      ],
      "package_name": "libheif",
      "purl": null
    }
  ],
  "cwes": [
    787
  ],
  "cvss_score": 7.4,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:H",
  "epss_score": 0.0048,
  "epss_percentile": 0.3993,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 28.120047516666666,
  "t0_at": "2026-09-18T15:56:41.773000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-09-18T15:56:41.773000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-09-18T15:56:41.773000+00:00",
      "url": "https://github.com/strukturag/libheif/security/advisories/GHSA-j264-xvrp-5v7q"
    }
  }
}

published 2026-10-01 00:35Z
last change 2026-10-21 04:45Z

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.