CVE-2026-75143

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-19. The CNA's CVSS baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: the CNA's CVSS, EPSS, GitHub Security Advisory

Also known asEUVD-2026-62580 (ENISA EUVD) · GHSA-7qc3-xqxj-426p (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

FFmpeg before commit 1c10bcc contains a heap buffer overflow in the RIST protocol reader (libavformat/librist.c). librist_read() ignored its size argument and copied the full received payload length into the caller-provided destination buffer, overflowing it when the payload exceeds the destination size. This is reachable via the async:rist:// URL scheme, where the async wrapper supplies a smaller buffer than the received payload. A remote RIST sender can trigger the overflow by sending a packet whose payload exceeds the caller buffer size.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
59
EG Risk 59/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.7% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.7%
EPSS %ILE
54th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-21). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 19, 2026

Last Modified

October 27, 2026

Advisory Details (3)

Auto-updated Nov 14, 2026
Patch available.
Web page

FFmpeg Heap Buffer Overflow via RIST Protocol Reader | Advisories | VulnCheck

https://www.vulncheck.com/advisories/ffmpeg-heap-buffer-overflow-via-rist-protocol-reader
Web page

avformat/librist: honor the caller buffer size in librist_read · 1c10bcc2e1 - FFmpeg/FFmpeg - FFmpeg Forgejo

https://code.ffmpeg.org/FFmpeg/FFmpeg/commit/1c10bcc2e17255dacb717a25ab3db142ce390602
Web page

#24089 - avformat/librist: honor the caller buffer size in librist_read - FFmpeg/FFmpeg - FFmpeg Forgejo

https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/24089

Vendor Advisories for CVE-2026-75143(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulibswscale4 (7:3.4.11-0ubuntu0.1+esm15) @ bionic2026-11-18ubuntu
ubuntulibswscale9 (7:8.0.1-3ubuntu2+esm4) @ resolute2026-11-18ubuntu

These rows come from Ubuntu. Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
ffmpeg7:5.1.3-1 ... 7:9.0.2-4 (63 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
ffmpeg7:7.1.1-1 ... 7:9.0.2-4 (27 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
ffmpeg7:7.1.1-1 ... 7:9.0.1-1 (19 versions)
  • every version up to 7:9.0.2-1: fixed in 7:9.0.2-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(2)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 18× in last 7d / 81× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 675 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 575 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-22 17:17 UTCGHSA enrichmentGHSA-7qc3-xqxj-426p · GitHub severity CRITICAL · GitHub CVSS 9.8
  2. 2026-11-21 17:37 UTCEchelonGraph re-scored
  3. 2026-11-21 17:37 UTCGHSA enrichmentGHSA-7qc3-xqxj-426p · GitHub severity CRITICAL · GitHub CVSS 9.8
  4. 2026-11-21 16:41 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  5. 2026-11-20 18:20 UTCEchelonGraph re-scored
  6. 2026-11-20 18:20 UTCGHSA enrichmentGHSA-7qc3-xqxj-426p · GitHub severity CRITICAL · GitHub CVSS 9.8
  7. 2026-11-20 16:38 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  8. 2026-11-19 19:04 UTCEchelonGraph re-scored
  9. 2026-11-19 19:04 UTCGHSA enrichmentGHSA-7qc3-xqxj-426p · GitHub severity CRITICAL · GitHub CVSS 9.8
  10. 2026-11-19 16:35 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  11. 2026-11-18 19:46 UTCEchelonGraph re-scored
  12. 2026-11-18 19:46 UTCVendor advisory
  13. 2026-11-18 19:46 UTCGHSA enrichmentGHSA-7qc3-xqxj-426p · GitHub severity CRITICAL · GitHub CVSS 9.8
  14. 2026-11-18 16:35 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  15. 2026-11-17 20:23 UTCEchelonGraph re-scored
  16. 2026-11-17 20:23 UTCVendor advisory
  17. 2026-11-17 20:23 UTCGHSA enrichmentGHSA-7qc3-xqxj-426p · GitHub severity CRITICAL · GitHub CVSS 9.8
  18. 2026-11-17 16:36 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  19. 2026-11-16 21:06 UTCEchelonGraph re-scored
  20. 2026-11-16 21:06 UTCVendor advisory
  21. 2026-11-16 21:06 UTCGHSA enrichmentGHSA-7qc3-xqxj-426p · GitHub severity CRITICAL · GitHub CVSS 9.8
  22. 2026-11-16 16:52 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  23. 2026-11-15 21:47 UTCEchelonGraph re-scored
  24. 2026-11-15 21:47 UTCVendor advisory
  25. 2026-11-15 21:47 UTCGHSA enrichmentGHSA-7qc3-xqxj-426p · GitHub severity CRITICAL · GitHub CVSS 9.8
Show 75 more
  1. 2026-11-15 17:02 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  2. 2026-11-14 22:29 UTCEchelonGraph re-scored
  3. 2026-11-14 22:29 UTCVendor advisory
  4. 2026-11-14 22:29 UTCGHSA enrichmentGHSA-7qc3-xqxj-426p · GitHub severity CRITICAL · GitHub CVSS 9.8
  5. 2026-11-14 16:41 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  6. 2026-11-13 23:03 UTCEchelonGraph re-scored
  7. 2026-11-13 23:03 UTCVendor advisory
  8. 2026-11-13 23:03 UTCGHSA enrichmentGHSA-7qc3-xqxj-426p · GitHub severity CRITICAL · GitHub CVSS 9.8
  9. 2026-11-13 16:57 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  10. 2026-11-12 23:13 UTCEchelonGraph re-scored
  11. 2026-11-12 23:13 UTCGHSA enrichmentGHSA-7qc3-xqxj-426p · GitHub severity CRITICAL · GitHub CVSS 9.8
  12. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  13. 2026-11-11 23:56 UTCEchelonGraph re-scored
  14. 2026-11-11 23:56 UTCVendor advisory
  15. 2026-11-11 23:56 UTCGHSA enrichmentGHSA-7qc3-xqxj-426p · GitHub severity CRITICAL · GitHub CVSS 9.8
  16. 2026-11-11 16:40 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  17. 2026-11-11 00:39 UTCEchelonGraph re-scored
  18. 2026-11-11 00:39 UTCVendor advisory
  19. 2026-11-11 00:39 UTCGHSA enrichmentGHSA-7qc3-xqxj-426p · GitHub severity CRITICAL · GitHub CVSS 9.8
  20. 2026-11-10 16:45 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  21. 2026-11-10 01:22 UTCEchelonGraph re-scored
  22. 2026-11-10 01:22 UTCGHSA enrichmentGHSA-7qc3-xqxj-426p · GitHub severity CRITICAL · GitHub CVSS 9.8
  23. 2026-11-09 16:36 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  24. 2026-11-09 02:05 UTCEchelonGraph re-scored
  25. 2026-11-09 02:05 UTCGHSA enrichmentGHSA-7qc3-xqxj-426p · GitHub severity CRITICAL · GitHub CVSS 9.8
  26. 2026-11-08 16:40 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  27. 2026-11-08 02:48 UTCEchelonGraph re-scored
  28. 2026-11-08 02:48 UTCGHSA enrichmentGHSA-7qc3-xqxj-426p · GitHub severity CRITICAL · GitHub CVSS 9.8
  29. 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  30. 2026-11-07 03:31 UTCEchelonGraph re-scored
  31. 2026-11-07 03:31 UTCGHSA enrichmentGHSA-7qc3-xqxj-426p · GitHub severity CRITICAL · GitHub CVSS 9.8
  32. 2026-11-06 17:55 UTCOSV refresh
  33. 2026-11-06 16:39 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  34. 2026-11-06 04:15 UTCEchelonGraph re-scored
  35. 2026-11-06 04:15 UTCGHSA enrichmentGHSA-7qc3-xqxj-426p · GitHub severity CRITICAL · GitHub CVSS 9.8
  36. 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  37. 2026-11-05 04:51 UTCEchelonGraph re-scored
  38. 2026-11-05 04:51 UTCGHSA enrichmentGHSA-7qc3-xqxj-426p · GitHub severity CRITICAL · GitHub CVSS 9.8
  39. 2026-11-04 16:36 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  40. 2026-11-04 05:34 UTCEchelonGraph re-scored
  41. 2026-11-04 05:34 UTCGHSA enrichmentGHSA-7qc3-xqxj-426p · GitHub severity CRITICAL · GitHub CVSS 9.8
  42. 2026-11-03 16:49 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  43. 2026-11-03 06:17 UTCEchelonGraph re-scored
  44. 2026-11-03 06:17 UTCVendor advisory
  45. 2026-11-03 06:17 UTCGHSA enrichmentGHSA-7qc3-xqxj-426p · GitHub severity CRITICAL · GitHub CVSS 9.8
  46. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  47. 2026-11-02 06:57 UTCEchelonGraph re-scored
  48. 2026-11-02 06:57 UTCVendor advisory
  49. 2026-11-02 06:57 UTCGHSA enrichmentGHSA-7qc3-xqxj-426p · GitHub severity CRITICAL · GitHub CVSS 9.8
  50. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  51. 2026-11-01 07:40 UTCEchelonGraph re-scored
  52. 2026-11-01 07:40 UTCVendor advisory
  53. 2026-11-01 07:40 UTCGHSA enrichmentGHSA-7qc3-xqxj-426p · GitHub severity CRITICAL · GitHub CVSS 9.8
  54. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  55. 2026-10-31 08:24 UTCEchelonGraph re-scored
  56. 2026-10-31 08:24 UTCVendor advisory
  57. 2026-10-31 08:24 UTCGHSA enrichmentGHSA-7qc3-xqxj-426p · GitHub severity CRITICAL · GitHub CVSS 9.8
  58. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  59. 2026-10-30 09:06 UTCEchelonGraph re-scored
  60. 2026-10-30 09:06 UTCVendor advisory
  61. 2026-10-30 09:06 UTCGHSA enrichmentGHSA-7qc3-xqxj-426p · GitHub severity CRITICAL · GitHub CVSS 9.8
  62. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  63. 2026-10-29 09:50 UTCEchelonGraph re-scored
  64. 2026-10-29 09:50 UTCVendor advisory
  65. 2026-10-29 09:50 UTCGHSA enrichmentGHSA-7qc3-xqxj-426p · GitHub severity CRITICAL · GitHub CVSS 9.8
  66. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  67. 2026-10-28 10:34 UTCEchelonGraph re-scored
  68. 2026-10-28 10:34 UTCVendor advisory
  69. 2026-10-28 10:33 UTCGHSA enrichmentGHSA-7qc3-xqxj-426p · GitHub severity CRITICAL · GitHub CVSS 9.8
  70. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  71. 2026-10-27 10:25 UTCEchelonGraph re-scored
  72. 2026-10-27 10:25 UTCVendor advisory
  73. 2026-10-27 10:25 UTCGHSA enrichmentGHSA-7qc3-xqxj-426p · GitHub severity CRITICAL · GitHub CVSS 9.8
  74. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  75. 2026-10-26 11:27 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-75143?
CVE-2026-75143 is a critical-severity vulnerability; its CVE record was published on August 19, 2026. FFmpeg before commit 1c10bcc contains a heap buffer overflow in the RIST protocol reader (libavformat/librist.c). librist_read() ignored its size argument and copied the full received payload length into the caller-provided destination buffer, overflowing it when the payload exceeds the destination…
When was CVE-2026-75143 made public?
CVE-2026-75143 was made public on August 4, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on August 19, 2026. EchelonGraph's copy of the record carries a last-modified date of October 27, 2026; the record at its source may have been updated since.
Is CVE-2026-75143 actively exploited?
CVE-2026-75143 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (54th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-75143?
CVE-2026-75143 has a CVSS base score of 9.8 (the CNA's own assessment, by vulncheck; NVD's own analysis pending).
How do I remediate CVE-2026-75143?
A fix for CVE-2026-75143 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-75143 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-75143

Explore →

Is Your Infrastructure Affected by CVE-2026-75143?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.