CVE-2026-44725Network attack vectorHinoki check available

Authenticated code execution via stale plugin grants

Published Aug 20, 2026 · Updated Aug 20, 2026

Code execution in EMQX before 5.8.11, 5.9.3, 5.10.4, 6.0.3, 6.1.2, and 6.2.1 allows remote authenticated users to run broker code via plugin upload. The plugin-install REST API and dashboard upload accept stale emqx ctl plugins allow grants and verify only the approved name and version string, not the uploaded tarball bytes, so a different package with the same filename is installed. Exploitation requires a compromised Dashboard administrator session or an API key with plugin-install permission plus a lingering allow entry, and successful exploitation runs attacker-controlled Erlang code with the privileges of the EMQX process.

CVSS severity6.6
Medium
EPSS probability0.25%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkAvailable
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Code execution in EMQX before 5.8.11, 5.9.3, 5.10.4, 6.0.3, 6.1.2, and 6.2.1 allows remote authenticated users to run broker code via plugin upload. The plugin-install REST API and dashboard upload accept stale emqx ctl plugins allow grants and verify only the approved name and version string, not the uploaded tarball bytes, so a different package with the same filename is installed. Exploitation requires a compromised Dashboard administrator session or an API key with plugin-install permission plus a lingering allow entry, and successful exploitation runs attacker-controlled Erlang code with the privileges of the EMQX process.

The record

CVE
CVE-2026-44725
Published
Aug 20, 2026
Updated
Aug 20, 2026
Vendor
EMQ
Product
EMQX
Classifications
CWE-672, CWE-345, T1505
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Aug 20, 2026CVE publishedPublication date reported by the CVE source.
  2. Aug 20, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=>= 5.10.0, < 5.10.4
  2. Affected versionversion=< 5.8.11
  3. Affected versionversion=>= 5.9.0, < 5.9.3
  4. Affected versionversion=>= 6.0.0, < 6.0.3
  5. Affected versionversion=>= 6.1.0, < 6.1.2
  6. Affected versionversion=>= 6.2.0, < 6.2.1

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

EMQ · EMQXversion=>= 5.10.0, < 5.10.4; version=< 5.8.11; version=>= 5.9.0, < 5.9.3; version=>= 6.0.0, < 6.0.3; version=>= 6.1.0, < 6.1.2; version=>= 6.2.0, < 6.2.1

Published CVSS scores

6.6GitHub, Inc.CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-672Operation on a Resource after Expiration or Release
CWE-345Insufficient Verification of Data Authenticity
T1505Server Software Component

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo