FFmpeg before commit b4c199c contains an incorrect integer narrowing conversion in the AV1 RTP packetizer (libavformat/rtpenc_av1.c). The OBU size is cast to long before comparison against the remaining frame size. On targets where long is 32 bits, including 64-bit Windows, sufficiently large OBU size values are sign-flipped by the narrowing cast, producing a negative value that passes the payload size check. This allows an oversized OBU to bypass the safety bound on affected platforms, leading to out-of-bounds memory access when the oversized value is subsequently used as a copy length.
CVE-2026-75145
Score 5.8 from GitHub Security Advisory published 2026-08-19. a secondary CVSS source baseline 5.8; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.8
- EG Score
- 5.8(high)
- EG Risk
- 31(Track)EG Risk 31/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity58% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 2%
- KEV
- Not listed
Published
August 19, 2026
Last Modified
August 19, 2026
Advisory Details (3)
Auto-updated Aug 19, 2026FFmpeg Integer Narrowing Conversion OOB Memory Access in AV1 RTP Packetizer | Advisories | VulnCheck
https://www.vulncheck.com/advisories/ffmpeg-integer-narrowing-conversion-oob-memory-access-in-av1-rtp-packetizer#24090 - avformat/rtpenc_av1: do not narrow the OBU size to (long) - FFmpeg/FFmpeg - FFmpeg Forgejo
https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/24090avformat/rtpenc_av1: do not narrow the OBU size to (long) · b4c199c590 - FFmpeg/FFmpeg - FFmpeg Forgejo
https://code.ffmpeg.org/FFmpeg/FFmpeg/commit/b4c199c5906ff53368926c2a5839881f41957e7fVendor Advisories for CVE-2026-75145(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 6× in last 7d / 6× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-20 15:37 UTCEG score recompute
- 2026-08-20 15:37 UTCGHSA enrichment
- 2026-08-19 17:38 UTCEG score recompute
- 2026-08-19 16:43 UTCEG score recompute
- 2026-08-19 16:43 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-75145?
When was CVE-2026-75145 disclosed?
Is CVE-2026-75145 actively exploited?
What is the CVSS score of CVE-2026-75145?
How do I remediate CVE-2026-75145?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-75145
Is Your Infrastructure Affected by CVE-2026-75145?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.