EMQ Technologies NanoMQ 0.24.6
Approved changes feed: RSS · Atom
cpe:2.3:a:emqx:nanomq:0.24.6:*:*:*:*:*:*:*
part: a version: 0.24.6 update: *
| Vendor | Emqx (3815afa5-363a-5807-a62b-81827f994785) |
|---|---|
| Product | Nanomq (b68622c8-7a3a-5b04-8aa1-92e50a89c529) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from NVD CPE 2.0 feed |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/emqx/nanomq |
purl2cpe | 2026-06-01 10:13:30.390673 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2025-68699 |
vulnerable | 2026-06-08 07:41:21.661976 |
NanoMQ $share/ Subscription Validation and Forwarding Parsing Inconsistency: NULL Pointer Increment Causes Crash
MEDIUM (6.5)
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.
Published: 2026-02-04T19:25:12.716Z
Updated: 2026-02-04T19:51:10.769Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.