# CVE-2026-92754: PatrowlManager through 1.8.4 Improper Access Control via users API

> Low-privilege authenticated users can enumerate all user accounts and their privilege flags due to a missing authorization check in the user listing API.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **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:** 16 Sep 2026
- **Updated:** 17 Sep 2026
- **Also known as:** GHSA-qqjf-qhrx-83xx

## What is CVE-2026-92754?

CVE-2026-92754 is a medium-severity missing authorization vulnerability in PatrowlManager, published on 16 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

PatrowlManager through 1.8.4 contains an improper access control vulnerability in the user listing API endpoint where the authorization decorator is commented out. Authenticated attackers with low-privilege accounts can enumerate all users and their privilege flags including superuser and staff status by accessing the endpoint.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-92754 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92754 is a medium-severity missing authorization vulnerability in PatrowlManager, published on 16 Sep 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-92754 exists.

Affected product: PatrowlManager. 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-92754/ (Markdown: https://insights.sbomify.com/CVE-2026-92754/index.md)
```

## Sources

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

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