Vulnerability in ffmpeg (DEBIAN-CVE-2026-12706)

Summary

Vulnerability in ffmpeg (DEBIAN-CVE-2026-12706). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 7:5.1.9-0+deb12u1 or later.

Original description

The description as published by the source.

A use-after-free vulnerability was found in FFmpeg's RASC video decoder. The decode_move() function initializes a read pointer into a decompressed buffer, but a subsequent reallocation of that same buffer during move-table processing leaves the pointer dangling. An attacker could exploit this by providing a specially crafted AVI file containing a malicious RASC video stream. When a user opens or plays the file, the decoder reads from freed heap memory, which could lead to a denial of service (crash).

Source: OSV.dev (Open Source Vulnerabilities) OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as DEBIAN-CVE-2026-12706 has been found in ffmpeg.
Risk of unauthorized operations or information disclosure.
What to do: upgrade ffmpeg to 7:5.1.9-0+deb12u1 or later.
If unsure, ask your IT team or search "ffmpeg DEBIAN-CVE-2026-12706" on the vendor's site.

DEBIAN-CVE-2026-12706 (ffmpeg)
Attack vector: remote (network-reachable) / unauthenticated
Patched: 7:5.1.9-0+deb12u1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (unclassified) exists in ffmpeg.

📍 Affected scope

Check the vendor advisory for the affected versions of ffmpeg.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 7:5.1.9-0+deb12u1.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'ffmpeg' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
grep -r 'ffmpeg' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で ffmpeg を grep し、稼働しているサービス・バージョンを把握する。
2
Apply patch patch
```
Upgrade ffmpeg to 7:5.1.9-0+deb12u1
```
ステージング環境で 7:5.1.9-0+deb12u1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Debian:12 ffmpeg

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7:5.1.9-0+deb12u1"}]}]

Debian:13 ffmpeg

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7:7.1.4-0+deb13u1"}]}]

Debian:14 ffmpeg

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7:8.1.1-1"}]}]

References

advisory security-tracker.debian.org