CVE-2025-69693

Out-of-bounds read in FFmpeg 8.0 and 8.0.1 RV60 video decoder (libavcodec/rv60dec.c). The quantization parameter (qp) validation at line 2267 only checks the lower bound (qp < 0) but is missing upper bound validation. The qp value can reach 65 (base value 63 from 6-bit frame header + offset +2 from read_qp_offset) while the rv60_qp_to_idx array has size 64 (valid indices 0-63). This results in out-of-bounds array access at lines 1554 (decode_cbp8), 1655 (decode_cbp16), and 1419/1421 (get_c4x4_set), potentially leading to memory disclosure or crash. A previous fix in commit 61cbcaf93f added validation only for intra frames. This vulnerability affects the released versions 8.0 (released 2025-08-22) and 8.0.1 (released 2025-11-20) and is fixed in git master commit 8abeb879df which will be included in FFmpeg 8.1.

Published: 2026-03-16 Last update: 2026-03-19 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-69693 is rated Low Risk (22/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.01%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-69693

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-03-17 — 0.01% —

Full EPSS history (1 record total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-69693

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.4 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:L Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:L)
Might cause slowdowns, glitches, or partial disruption—not a full brick.
 2.8 2.5 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2025-69693

OS Trackers for CVE-2025-69693

vendor priority summary link
alpine — CVE-2025-69693: 1 source package rows (ffmpeg); 11 state rows across 2 repos (3.23-community, edge-community); fixed 0, open 11. https://security.alpinelinux.org/vuln/CVE-2025-69693
debian unimportant CVE-2025-69693 unimportant priority: Debian including 1 source packages (ffmpeg), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2025-69693
redhat medium — https://access.redhat.com/security/cve/CVE-2025-69693
ubuntu medium CVE-2025-69693 medium priority: Ubuntu including 2 source packages (ffmpeg, libav), 12 status rows across 8 suites (bionic, focal, jammy, noble, questing, trusty, upstream, xenial): not-affected 7, DNE 3, released 2. https://ubuntu.com/security/CVE-2025-69693

Affected software / configurations for CVE-2025-69693

Vendor Product Version Raw CPE
ffmpeg ffmpeg 8.0 cpe:2.3:a:ffmpeg:ffmpeg:8.0:*:*:*:*:*:*:*
ffmpeg ffmpeg 8.0.1 cpe:2.3:a:ffmpeg:ffmpeg:8.0.1:*:*:*:*:*:*:*

References for CVE-2025-69693

cvelogic Threat Intelligence