Skip to main content
Mallory
UnratedVulnerability

CVE-2025-55662: Divide-by-Zero in GPAC/MP4Box gf_opus_parse_packet_header

Updated 5 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS-Not scored
EPSS-30-day exploit probability
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2025-55662CWE-369

CVE-2025-55662 is a divide-by-zero vulnerability in GPAC/MP4Box affecting gpac/gpac prior to fix commit ff8249a407685d00ceb5f4d2a798b9cad195140e. The flaw is in gf_opus_parse_packet_header() in media_tools/av_parsers.c while processing an MP4 file containing an Opus audio track with malformed packet or header parameters. Specifically, critical Opus packet fields such as nb_frames are not validated before being used in arithmetic; the available reporting notes logic equivalent to computing values derived from header->nb_frames without first ensuring the field is non-zero and otherwise valid. When MP4Box reaches the Opus dump path on a crafted file, this can trigger a division by zero and terminate the process with a floating-point exception, with published traces pointing to media_tools/av_parsers.c:11479 and call paths including gf_inspect_dump_opus_internal() and dump_isom_opus().

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation causes MP4Box to crash while processing a malicious MP4 file, resulting in a denial of service for the affected process. Based on the provided information, the demonstrated impact is process termination via floating-point exception during file parsing/inspection; there is no specific evidence in the supplied content of code execution, privilege escalation, or memory corruption beyond the crash condition.

Mitigation

If you can’t patch tonight, do this now.

Until a fixed version is deployed, avoid processing untrusted or externally supplied MP4 files containing Opus audio tracks with MP4Box, especially along dump/inspection workflows such as XML dumping. If operationally necessary, restrict who can submit files for processing, isolate MP4Box in a sandboxed environment, and use crash containment controls to limit denial-of-service impact. Input pre-validation of media files may reduce exposure, but the authoritative mitigation is patching.

Remediation

Patch, then assume compromise.

Upgrade GPAC/MP4Box to a version that includes the fix for CVE-2025-55662, or apply the upstream patch associated with commit ff8249a407685d00ceb5f4d2a798b9cad195140e. The underlying remediation is to validate Opus packet/header fields, including ensuring nb_frames and related values are within expected bounds before they are used in arithmetic in gf_opus_parse_packet_header().

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2025-55662 exploited in the wild?
As of Jun 14, 2026, Mallory has no reports of CVE-2025-55662 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2025-55662?
As of Jun 14, 2026, Mallory has found no public exploit for CVE-2025-55662.
Is there a patch for CVE-2025-55662?
Upgrade GPAC/MP4Box to a version that includes the fix for CVE-2025-55662, or apply the upstream patch associated with commit ff8249a407685d00ceb5f4d2a798b9cad195140e. The underlying remediation is to validate Opus packet/header fields, including ensuring nb_frames and related values are within expected bounds before they are used in arithmetic in gf_opus_parse_packet_header().
Activity feed

Recent activity

2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

View more in app →

No news coverage yet. Advisories and community discussion only.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity2Community discussion across Reddit, Mastodon, and other social sources.