Quick answers
- Is CVE-2026-95847 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-95847 being exploited in the wild.
- How severe is CVE-2026-95847?
- Informational severity, published 23 September 2026.
- Which products and versions are affected?
- Moquette before 0.18.1.
- Is there a fix for CVE-2026-95847?
- A patch was published on 2026-07-19. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-95847 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-95847?
- Check whether you run Moquette at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The H2PersistentQueue constructs message map and metadata map names by simple string concatenation using a shared "queue_" prefix, allowing a client ID ending in "_meta" to collide with another client's metadata map. Two sessions read/write the same MVStore map with incompatible value types (Long vs EnqueuedMessage), corrupting queue head/tail pointers. The fix namespaces metadata maps to "queuemeta_<id>" with automatic migration of existing queues, eliminating collision by construction.
Affected products
- Moquette Moquette before 0.18.1
Timeline
- 2026-09-23: disclosed
- 2026-07-19: patched