CVE-2025-68699

MEDIUMNVD 6.56.5
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 6.5 under NVD CVSS v3. EPSS exploit probability: 0.3% (25th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3

Also known asEUVD-2025-206782 (ENISA EUVD)Source: ENISA EUVD

6.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 6.5Exploit: None knownExposed services: Not assessed

The CVE record names the fixed release — apply it.

NanoMQ MQTT Broker (NanoMQ) is an all-around Edge Messaging Platform. In version 0.24.6, NanoMQ has a protocol parsing / forwarding inconsistency when handling shared subscriptions ($share/). A malformed SUBSCRIBE topic such as $share/ab (missing the second /) is not strictly validated during the subscription stage, so the invalid Topic Filter is stored into the subscription table. Later, when any PUBLISH matches this subscription, the broker send path (nmq_pipe_send_start_v4/v5) performs a second $share/ parsing using strchr() and increments the returned pointer without NULL checks. If the second strchr() returns NULL, sub_topic++ turns the pointer into an invalid address (e.g. 0x1). This invalid pointer is then passed into topic_filtern(), which triggers strlen() and crashes with SIGSEGV. The crash is stable and remotely triggerable. This issue has been patched in version 0.24.7.

CVSS v3
6.5
EG Score
6.5MEDIUMmedium confidence
EG Risk
29
EG Risk 29/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)
Severity65% × 45%
Impact severity (EG Severity): CVSS 6.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 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: The CVE record names the fixed release. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
25th
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 (6.5): severity, escalated by confirmed exploitation. This CVE's 6.5 is its impact severity (EG Severity), not escalated.

EG Severity
6.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS. 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 every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade 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 every mission impact level.

The CVE record names the fixed release. Apply it within your standard update timelines.

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.

The score's inputs: 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

February 4, 2026

Last Modified

June 17, 2026

Advisory Details (2)

Auto-updated Aug 6, 2026
Fix named in the CVE record. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)

NanoMQ $share/ Subscription Validation and Forwarding Parsing Inconsistency: NULL Pointer Increment Causes Crash · Advisory · nanomq/nanomq · GitHub

https://github.com/nanomq/nanomq/security/advisories/GHSA-qv5f-c6v2-2f8h
GitHub commit

commit 89d68d678e7f (nanomq/nanomq)

Fix landed in nanomq/nanomq commit 89d68d678e7f — awaiting tagged release

https://github.com/nanomq/nanomq/commit/89d68d678e7f841ae7baa45cba8d9bc7ddc9ef4b

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 37× 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 99 of 199 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. 1 repeat row among the latest 100 is merged into the row it repeats. The 100 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2025-68699?
CVE-2025-68699 is a medium-severity vulnerability; its CVE record was published on February 4, 2026. NanoMQ MQTT Broker (NanoMQ) is an all-around Edge Messaging Platform. In version 0.24.6, NanoMQ has a protocol parsing / forwarding inconsistency when handling shared subscriptions ($share/). A malformed SUBSCRIBE topic such as $share/ab (missing the second /) is not strictly validated during the…
When was the CVE record for CVE-2025-68699 published?
The CVE record for CVE-2025-68699 was published on February 4, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of June 17, 2026; the record at its source may have been updated since.
Is CVE-2025-68699 actively exploited?
CVE-2025-68699 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (25th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-68699?
CVE-2025-68699 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2025-68699?
The CVE record for CVE-2025-68699 names the fix: "This issue has been patched in version 0.24.7."

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-68699

Explore →

Is Your Infrastructure Affected by CVE-2025-68699?

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