# io.moquette:moquette-broker has a Missing Authorization issue

Advisory record · `GHSA-9jjc-fw8x-fmwx`

- **Identifiers:** `GHSA-9jjc-fw8x-fmwx` · `CVE-2026-85058`
- **State:** Confirmed
- **Severity:** CVSS 7.5 High
- **Critical:** No
- **Weakness (CWE):** [CWE-862](https://cwe.mitre.org/data/definitions/862.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 18 Sept 2026
- **Updated:** 18 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 18 Sept 2026, 17:58 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `io.moquette:moquette-broker` (Maven): affected `<0.18.1`; fixed in `0.18.1`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Moquette MQTT broker (io.moquette:moquette-broker) before 0.18.1 does not check write permissions when publishing Will messages for disconnected clients, so the ACL is bypassed for those messages. An unauthenticated attacker on a broker with anonymous access enabled (the default) can set a restricted topic as the Will topic and drop the TCP connection to inject messages into that topic. Upgrade to version 0.18.1. The source also describes a possible code execution impact on subscribers that deserialize message payloads, but it is not a broker-side effect.

Written 2 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 7.5 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0057, the 47th percentile, on 7 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:16 UTC: First seen by agentprime
- 31 Oct 2026, 14:16 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-9jjc-fw8x-fmwx)

## Sources

- [GitHub Advisory Database: GHSA-9jjc-fw8x-fmwx](https://github.com/advisories/GHSA-9jjc-fw8x-fmwx)
- [OSV: GHSA-9jjc-fw8x-fmwx](https://osv.dev/vulnerability/GHSA-9jjc-fw8x-fmwx)
- <https://github.com/moquette-io/moquette/security/advisories/GHSA-9jjc-fw8x-fmwx>
- <https://github.com/moquette-io/moquette/commit/e23df019f6a11e22c7d2047d4f86d07095466c97>
- <https://github.com/moquette-io/moquette/commit/f5a323fe782d1505c0097498cb22eb6ec6c96973>
- <https://github.com/moquette-io/moquette>
- <https://github.com/moquette-io/moquette/releases/tag/v0.18.1>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-9jjc-fw8x-fmwx>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-9jjc-fw8x-fmwx/>. Everything for agents: <https://agentprime.io/llms.txt>.