Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 6.5

Memory exhaustion when parsing a crafted iloc box

GHSA-3243-948x-x627

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (heifer-isobmff 0.3.27), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
6.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

`heifer-isobmff` read the item and extent counts of the `iloc` box (item locations) from the file and allocated memory for them before checking that the box was large enough to hold that many entries. Extents that declare no field at all take zero bytes each, so a small crafted file could declare an enormous number of them. A 42 KB file made parsing allocate several gigabytes, which can exhaust memory and abort the process. Any application that parses untrusted HEIF/HEIC files with `heifer-isobmff`, directly or through the `heifer` crate, is affected: `HeifFile::parse` and every decoding and metadata function built on it. The flaw was corrected in 0.3.27 (commit `1a8426e`): item and extent counts are bounded by the size of the box, extents that carry no field are rejected, and the total number of extents is capped.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from osv record RUSTSEC-2026-0458

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-3243-948x-x627

Advisory: Memory exhaustion when parsing a crafted `iloc` box
IDs: GHSA-3243-948x-x627
Record: https://patchnext.com/advisories/rustsec-2026-0458 (revision 1, source checked 10 Nov 2026, 06:45 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: heifer-isobmff 0.3.27. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io heifer-isobmff: affected >= 0.0.0-0, < 0.3.27; fixed in 0.3.27

## Suggested inspection (read-only)
- crates.io heifer-isobmff: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on heifer-isobmff.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/RUSTSEC-2026-0458 (OSV record RUSTSEC-2026-0458 lists affected ranges: crates.io heifer-isobmff >=0.0.0-0 <0.3.27 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…