Skip to main content

Manticore Search EUVDEUVD-2026-81059

| CVE-2026-92796 HIGH
Incorrect Authorization (CWE-863)
2026-09-16 VulnCheck GHSA-mwg5-jprr-5586
8.7
CVSS 4.0 · Vendor: VulnCheck
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate as read-only user
  2. Delivery
    Send multi-statement SQL request
  3. Exploit
    Append SELECT on credential tables
  4. Execution
    Extract administrator password hashes
  5. Impact
    Re-authenticate as admin via stolen hash

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization logic validation
MITRE ATT&CK

1 technique across 1 tactic: Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires a valid but low-privileged (read-only) authenticated account on a Manticore Search instance running an affected version (27.0.0 through 28.4.3) that accepts multi-statement SQL requests over the MySQL protocol interface; the attacker crafts a request appending extra SELECT statements after the first, whose permissions are never re-validated. Limiting factors: an existing account with SQL access is needed (PR:L, not unauthenticated), and the instance must permit multi-statement queries; upgrading to 28.4.4 fully remediates. No user interaction and no non-default feature toggle beyond standard SQL access are required.

Impact

This is a genuine, actionable priority rather than a high-CVSS-but-low-real-risk paper finding. The vendor CVSS 4.0 score is 8.7 (AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H), and the key aggravating signals reinforce each other: publicly available exploit code exists (geo-chen/oss write-up), a patch is available, and the flaw was reported by a credible research org (VulnCheck). The CVSS vector cleanly matches the description - network-reachable, low attack complexity, no user interaction, and PR:L (a low-privileged/read-only account is required, so this is authenticated). The one honest caveat is that the DIRECT technical impact of the bug is unauthorized READ of credential tables (confidentiality); the VI:H/VA:H integrity/availability ratings are downstream consequences of stealing admin password hashes and re-authenticating as administrator (pass-the-hash), not a separate memory-corruption or write primitive - a defensible but slightly generous rating. No EPSS score and no CISA KEV entry were provided in the input, so there is no evidence of active in-the-wild exploitation; the risk here is driven by public POC availability plus low exploitation prerequisites, not confirmed exploitation. Overall: prioritize patching to 28.4.4 because a working exploit is public and the privilege bar is merely 'any authenticated read-only user.'

Exploit ScenarioDerived

An attacker holding any low-privileged, read-only Manticore Search account sends a multi-statement SQL request where a permitted first statement is followed by an appended SELECT against internal credential tables; because permissions are only validated for the first statement, the extra SELECT executes and returns administrator password hashes. The attacker then authenticates as an administrator using the stolen hash (no plaintext recovery needed), achieving full control. Public exploit code for this technique already exists.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
1 PoC candidate (unverified) Patch available 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 16, 2026

Multi-statement SQL authorization bypass in Manticore Search 27.0.0 through 28.4.3 lets an authenticated read-only user escalate to full administrative control: the server validates permissions only for the first statement in a batch, so appending additional SELECT statements exposes system credential tables and their password hashes, which can be replayed to authenticate as an administrator without cracking any plaintext. No user interaction is required, and publicly available exploit code exists, though no confirmed active exploitation (CISA KEV) has been reported; the only prerequisite is an existing low-privileged account with SQL access over the MySQL-protocol interface. This is a genuine, actionable priority rather than a high-CVSS-but-low-real-risk paper finding.

RemediationAI

Upgrade to Manticore Search 28.4.4 or later: vendor-released patch version 28.4.4 contains the fix in src/auth/auth_proto_mysql.cpp (lines 408-418 on the release-28.4.4 branch, github.com/manticoresoftware/manticoresearch/blob/release-28.4.4/src/auth/auth_proto_mysql.cpp#L408-L418), and the upstream issue is github.com/manticoresoftware/manticoresearch/issues/4706. Remediation should not stop at the binary upgrade: because the vulnerability enables extraction and replay of password hashes, rotate every administrator (and any other) credential on affected instances and remove or re-create stale accounts, since hash-based access may succeed without any plaintext ever being recovered. As compensating controls until patching is complete, restrict network access to the MySQL-protocol listener (default port 9306) to trusted hosts via firewall or bind-address rules - the trade-off is that remote MySQL clients, BI tools and application integrations will lose connectivity - and, where a proxy or client library sits in front of the service, reject batched multi-statement requests so only one statement per round trip is accepted, understanding that this can break legitimate batch scripts and ORMs that rely on multi-statement packets. Reduce reliance on read-only-but-SQL-capable accounts where they are not operationally required, enable query logging and review it for concatenated or unusually long statement batches, and treat any instance that was exposed with such an account as potentially compromised for credential-rotation purposes. Publicly available exploit code exists for this flaw, so patching should be prioritized rather than scheduled routinely; no confirmed active exploitation (CISA KEV) has been reported at time of analysis.

Affected VersionsENISA

Manticore Search 27.0.0 <28.4.4

Affected Packages

euvd manticore_search fix: 28.4.4

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Manticore Search implements a MySQL-compatible wire protocol listener (typically on port 9306) so standard MySQL clients can submit SQL statements. The flaw is rooted in CWE-863 (Incorrect Authorization): when a client sends a multi-statement request, the authorization routine in src/auth/auth_proto_mysql.cpp checks the privileges of only the first statement, and the remaining statements in the same batch are then executed under the connection's existing session without a per-statement permission re-check. Because the credential tables are reachable through unprivileged SQL, a read-only account can append SELECT statements that dump the stored password hashes used for account authentication. Those hashes are sufficient to authenticate directly (pass-the-hash), which is why the description notes administrators can be impersonated without recovering plaintext. The published CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N, with High confidentiality, integrity and availability impact) matches the independent CVSS 3.1 assessment (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H): remotely reachable, no attack complexity or preconditions beyond a valid low-privileged SQL account, no user interaction, and complete compromise of the instance once admin-level access is obtained.

Know when Manticore Search gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (VulnCheck) PRIMARY 8.7 HIGH
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
vuln.today AI 8.8 HIGH

Network-reachable SQL interface, low complexity, PR:L for the required read-only account; C:H from credential-table disclosure, with I:H/A:H reflecting the resulting administrator takeover via stolen hashes.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
Low
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
High
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

DescriptionCVE.org

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.

Technical POC Analysis

CWE-863 (Incorrect Authorization).

Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.

Latest POC

1 PoC candidate from github (unverified)

Sign in to open the public PoC links collected for this CVE.

Executive ViewAI

Why It Matters

Manticore Search versions 27.0.0 through 28.4.3 contain a SQL authorization bypass that lets a user holding only a limited SQL account elevate to full administrative control of the search cluster and read stored credential hashes that can be replayed as an administrator. Any team running these versions in production is exposed wherever a low-privilege SQL account exists, which is common in shared search platforms and multi-team deployments. Because administrative takeover can yield reusable credentials beyond the search tier, this warrants priority remediation rather than routine backlog handling.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.3%
Top 79% exploitable
Prevalence
Medium
popular open-source search/database engine (Sphinx successor), moderate but niche adoption
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC Yes
EPSS 0.3%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
Poc
System Exposure· derived
Open
Automatable· derived
No
Human Impact
High

Priority Score

64
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +44
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy