# CVE-2026-92796: Manticore Search 27.0.0 before 28.4.4 Multi-Statement Authorization Bypass

> Read-only users can bypass authorization in multi-statement requests to read credential tables and escalate privileges to administrator.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/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:** 21 Sep 2026
- **Also known as:** GHSA-mwg5-jprr-5586

## What is CVE-2026-92796?

CVE-2026-92796 is a high-severity missing authorization vulnerability in manticoresoftware Manticore Search, published on 16 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Manticore Search versions 27.0.0 before 28.4.4 fail to validate permissions for all statements in multi-statement SQL requests, allowing read-only users to execute unauthorized queries. Attackers can append additional SELECT statements after the first statement to read credential tables and obtain password hashes that authenticate as administrators without plaintext recovery.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-92796 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92796 is a high-severity missing authorization vulnerability in manticoresoftware Manticore Search, 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-92796 exists.

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

## Sources

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

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