CVE-2026-38348
massInteger Overflow DoS in FFmpeg libswscale via Crafted Images
CVE-2026-38348 is an integer overflow (CWE-190) in the libswscale/utils.c component of FFmpeg, identified in development build N-122528-gdd2976b9e1. An attacker triggers the flaw by supplying a crafted image file to software that processes it with the vulnerable libswscale scaling code. Successful exploitation causes a denial of service: the CVSS vector (AV:N/AC:L/PR:N/UI:N, availability-only) indicates a remote, unauthenticated attacker can render the affected service unavailable with high availability impact but no confidentiality or integrity loss. Any deployment running FFmpeg builds containing the vulnerable libswscale code — whether used directly or bundled inside other media applications, media servers, or transcoding pipelines — is potentially affected. No public proof-of-concept, in-the-wild exploitation, or KEV listing is known, and EPSS estimates only a 0.3% probability of exploitation within 30 days.
What to do: Inventory where FFmpeg or bundled libswscale code is deployed (distribution packages, Docker images, media servers, transcoding pipelines) and update to a patched FFmpeg build as soon as the fix is incorporated into a release you use. Until patched, limit or sandbox processing of untrusted image files — for example, run transcoding workers in resource-capped, isolated environments so a crafted image cannot take down shared services. Watch vendor advisories for the confirmed affected/fixed version ranges, since only a development build identifier is currently documented.
| FFmpeg project FFmpeg (libswscale/utils.c) | — |
Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.
An integer overflow in the libswscale/utils.c component of FFmpeg N-122528-gdd2976b9e1 allows attackers to cause a Denial of Service (DoS) via supplying a crafted image file.
- Weakness
- CWE-190
- Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
In the news0 stories
No ingested article mentions this CVE yet.