CVE-2024-10525

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 59% (99th percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 9.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-10-30) is not newer than that change (2025-11-03), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this weekElevated

Also known asEUVD-2024-33469 (ENISA EUVD) · GHSA-cm54-mprw-5279 (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 exploitation likelihood — EPSS 59%
CISA-KEV: Not listedEPSS PROB: 59%CVSS: 9.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

In Eclipse Mosquitto, from version 1.3.2 through 2.0.18, if a malicious broker sends a crafted SUBACK packet with no reason codes, a client using libmosquitto may make out of bounds memory access when acting in its on_subscribe callback. This affects the mosquitto_sub and mosquitto_rr clients.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
83
EG Risk 83/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.
Exploitation59% × 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 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: 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
59%
EPSS %ILE
99th
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.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
59% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-02). 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: 14 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 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)14 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 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

October 30, 2024

Last Modified

November 3, 2025

Advisory Details (4)

Auto-updated Oct 9, 2026
Patch available. Sources: github_commit.
Web pageMentions a patch (unverified)

[SECURITY] [DLA 4059-1] mosquitto security update

https://lists.debian.org/debian-lts-announce/2025/02/msg00022.html
Web page

Version 2.0.19 released. | Eclipse Mosquitto

https://mosquitto.org/blog/2024/10/version-2-0-19-released/
Web page

Heap Buffer Overflow in my_subscribe_callback Function in Eclipse Mosquitto v2.0.18-4-g15292b20 (#190) · Issues · Eclipse Projects Security / vulnerability-reports · GitLab

https://gitlab.eclipse.org/security/vulnerability-reports/-/issues/190
GitHub commit

commit 8ab20b4ba420 (eclipse-mosquitto/mosquitto)

Fix landed in eclipse-mosquitto/mosquitto commit 8ab20b4ba420 — awaiting tagged release

https://github.com/eclipse-mosquitto/mosquitto/commit/8ab20b4ba4204fdcdec78cb4d9f03c944a6e0e1c

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntumosquitto-dev (1.4.15-2ubuntu0.18.04.3+esm2) @ bionic2026-11-02ubuntu

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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
mosquitto2.0.11-1, 2.0.11-1+deb11u1
  • every version up to 2.0.11-1+deb11u2: fixed in 2.0.11-1+deb11u2
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
mosquitto2.0.11-1.2, 2.0.11-1.2+deb12u1
  • every version up to 2.0.11-1.2+deb12u2: fixed in 2.0.11-1.2+deb12u2
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
mosquitto—
  • every version up to 2.0.20-1: fixed in 2.0.20-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
mosquitto—
  • every version up to 2.0.20-1: fixed in 2.0.20-1
—

Weakness Classification(2)

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

All Vendor Advisories

(1)

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 20× in last 7d / 79× 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 96 of 226 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. 4 repeat rows among the latest 100 are merged into the row they repeat. The 130 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2024-10525?
CVE-2024-10525 is a critical-severity vulnerability; its CVE record was published on October 30, 2024. In Eclipse Mosquitto, from version 1.3.2 through 2.0.18, if a malicious broker sends a crafted SUBACK packet with no reason codes, a client using libmosquitto may make out of bounds memory access when acting in its on_subscribe callback. This affects the mosquitto_sub and mosquitto_rr clients.
When was CVE-2024-10525 made public?
CVE-2024-10525 was made public on October 30, 2024: that is the date its CVE record's CNA, Eclipse Foundation, gives for when the vulnerability was made public. The CVE record itself was published on October 30, 2024. EchelonGraph's copy of the record carries a last-modified date of November 3, 2025; the record at its source may have been updated since.
Is CVE-2024-10525 actively exploited?
CVE-2024-10525 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 59% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-10525?
CVE-2024-10525 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2024-10525?
A fix for CVE-2024-10525 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2024-10525?

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