CVE-2024-8375

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.8 under NVD CVSS v3. EPSS exploit probability: 0.1% (1st percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 6.1 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2024-09-19) is not newer than that change (2025-07-22), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week
7.8EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 7.8Exploit: None knownExposed services: Not assessed

An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.

There exists a use after free vulnerability in Reverb. Reverb supports the VARIANT datatype, which is supposed to represent an arbitrary object in C++. When a tensor proto of type VARIANT is unpacked, memory is first allocated to store the entire tensor, and a ctor is called on each instance. Afterwards, Reverb copies the content in tensor_content to the previously mentioned pre-allocated memory, which results in the bytes in tensor_content overwriting the vtable pointers of all the objects which were previously allocated. Reverb exposes 2 relevant gRPC endpoints: InsertStream and SampleStream. The attacker can insert this stream into the server’s database, then when the client next calls SampleStream they will unpack the tensor into RAM, and when any method on that object is called (including its destructor) the attacker gains control of the Program Counter. We recommend upgrading past git commit  https://github.com/google-deepmind/reverb/commit/6a0dcf4c9e842b7f999912f792aaa6f6bd261a25

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/100

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 computed (value × EchelonGraph’s weight)
Severity78% × 45%
The EG Score, 7.8 of 10.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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: An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines until it ships, then apply the release.
EPSS PROB
0.1%
EPSS %ILE
1st
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines until it ships, then apply the release.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (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

September 19, 2024

Last Modified

July 22, 2025

Advisory Details (2)

Auto-updated Oct 2, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
Web page

Vulnerability in Reverb object deserialization · Issue #141 · google-deepmind/reverb · GitHub

https://github.com/google-deepmind/reverb/issues/141
GitHub commit

commit 6a0dcf4c9e84 (google-deepmind/reverb)

Fix landed in google-deepmind/reverb commit 6a0dcf4c9e84 — awaiting tagged release

https://github.com/google-deepmind/reverb/commit/6a0dcf4c9e842b7f999912f792aaa6f6bd261a25

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
pipdm-reverb—ghsa
pipdm-reverb-nightly—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 1 ecosystem)
PyPI(2)
PackageVulnerable rangeFix by version rangeDependents
dm-reverb0.1.0 ... 0.9.0rc1 (50 versions)
  • every version through 0.14.0: no fix on record
—
dm-reverb-nightly0.11.0.dev20221208 ... 0.9.0.dev20221207 (457 versions)
  • every version through 0.15.0.dev20240214: no fix on record
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 33× 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 it from the CNA feed. 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). Most recent first.

Showing the most recent 89 of 172 refreshes 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. 11 repeat rows among the latest 100 are merged into the row they repeat. The 83 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-12 17:31 UTCEG score recompute
  2. 2026-10-12 16:32 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  3. 2026-10-11 21:00 UTCEG score recompute
  4. 2026-10-11 19:10 UTCEG score recompute
  5. 2026-10-11 15:51 UTCEG score recompute
  6. 2026-10-11 13:46 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  7. 2026-10-10 19:58 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  8. 2026-10-10 13:03 UTCOSV refresh
  9. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  10. 2026-10-08 17:08 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  11. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  12. 2026-10-06 15:16 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  13. 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  14. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  15. 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  16. 2026-10-02 17:56 UTCEG score recompute
  17. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  18. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  19. 2026-09-29 15:18 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  20. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  21. 2026-09-27 13:44 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  22. 2026-09-26 15:57 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  23. 2026-09-24 14:02 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  24. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  25. 2026-09-22 14:47 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
Show 64 more
  1. 2026-09-20 22:57 UTCOSV refresh
  2. 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  3. 2026-09-19 15:41 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  4. 2026-09-18 19:26 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  5. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  6. 2026-09-16 05:13 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  7. 2026-09-15 03:08 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  8. 2026-09-13 16:45 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  9. 2026-09-12 14:59 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  10. 2026-09-11 14:51 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  11. 2026-09-11 09:35 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  12. 2026-09-10 09:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  13. 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  14. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  15. 2026-09-04 13:59 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  16. 2026-09-04 05:05 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  17. 2026-09-02 14:10 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  18. 2026-09-01 22:27 UTCOSV refresh
  19. 2026-09-01 13:52 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  20. 2026-08-30 19:16 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  21. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  22. 2026-08-28 21:39 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  23. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  24. 2026-08-25 13:47 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  25. 2026-08-24 14:15 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  26. 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  27. 2026-08-21 23:47 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  28. 2026-08-20 22:54 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  29. 2026-08-19 17:02 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  30. 2026-08-17 13:46 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  31. 2026-08-16 14:55 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  32. 2026-08-16 02:13 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  33. 2026-08-16 00:07 UTCOSV refresh
  34. 2026-08-15 01:29 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  35. 2026-08-13 21:59 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  36. 2026-08-12 13:49 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  37. 2026-08-10 23:58 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  38. 2026-08-09 13:45 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  39. 2026-08-08 16:35 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  40. 2026-08-06 13:45 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  41. 2026-08-05 19:16 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  42. 2026-08-04 15:08 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  43. 2026-08-04 10:37 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  44. 2026-08-03 10:35 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  45. 2026-08-02 02:25 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  46. 2026-08-01 04:14 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  47. 2026-07-31 18:12 UTCOSV refresh
  48. 2026-07-30 16:26 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  49. 2026-07-30 01:29 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  50. 2026-07-28 15:35 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  51. 2026-07-27 14:12 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  52. 2026-07-23 14:17 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  53. 2026-07-23 02:46 UTCEG score recompute▲ 1.70
  54. 2026-07-22 14:07 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  55. 2026-07-21 15:24 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  56. 2026-07-20 17:07 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  57. 2026-07-19 14:30 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  58. 2026-07-19 02:28 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  59. 2026-07-18 10:03 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  60. 2026-07-16 17:02 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  61. 2026-07-15 16:57 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  62. 2026-07-15 01:59 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  63. 2026-07-14 01:00 UTCOSV refresh
  64. 2026-07-13 22:29 UTCEPSS rescoreEPSS 0.1% · 2nd percentile

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2024-8375?
CVE-2024-8375 is a high-severity vulnerability; its CVE record was published on September 19, 2024. There exists a use after free vulnerability in Reverb. Reverb supports the VARIANT datatype, which is supposed to represent an arbitrary object in C++. When a tensor proto of type VARIANT is unpacked, memory is first allocated to store the entire tensor, and a ctor is called on each instance.…
When was CVE-2024-8375 made public?
CVE-2024-8375 was made public on August 28, 2024: that is the date its CVE record's CNA, Google LLC, gives for when the vulnerability was made public. The CVE record itself was published on September 19, 2024. EchelonGraph's copy of the record carries a last-modified date of July 22, 2025; the record at its source may have been updated since.
Is CVE-2024-8375 actively exploited?
CVE-2024-8375 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-8375?
CVE-2024-8375 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2024-8375?
An upstream fix for CVE-2024-8375 has been merged but is not yet in a tagged release. Until it ships, restrict network exposure of the affected system or apply the vendor's mitigation, then update to the release that contains the fix.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-8375

Explore →

Is Your Infrastructure Affected by CVE-2024-8375?

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

Book a Demo →Browse All CVEs