# CVE-2026-6564: EMQ EMQX Enterprise Session Handling improper authorization

> Remote attackers can bypass authorization checks in EMQX Enterprise session handling to access restricted resources.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Apr 2026
- **Updated:** 20 Apr 2026
- **Also known as:** GHSA-vqmj-h423-xx64

## What is CVE-2026-6564?

CVE-2026-6564 is a medium-severity missing authorization vulnerability in EMQX Enterprise, published on 19 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was found in EMQ EMQX Enterprise up to 6.1.0. The impacted element is an unknown function of the component Session Handling. The manipulation results in improper authorization. It is possible to launch the attack remotely. The exploit has been made public and could be used. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-285 (Improper Authorization), CWE-266 (Incorrect Privilege Assignment)

## Which versions are affected by CVE-2026-6564?


## How do I fix CVE-2026-6564?

No fix has been published for CVE-2026-6564 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-6564 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-6564 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-6564 and fix it if it is affected.

What it is: CVE-2026-6564 is a medium-severity missing authorization vulnerability in EMQX Enterprise, published on 19 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-6564 exists.

Affected product: EMQX Enterprise. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-6564/ (Markdown: https://insights.sbomify.com/CVE-2026-6564/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-6564
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-6564
- OSV: https://osv.dev/vulnerability/CVE-2026-6564

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-6564/
Summaries are generated and may contain mistakes; the official description above is the record.