CVE-2026-10814Public exploit

Local privilege escalation via truncated grantee hash

Published Jun 4, 2026 · Updated Jun 4, 2026

Weak hashing in Milvus 2.6.0 through 2.6.13 allows local users to inherit another role's privileges through a grantee-ID collision. The RBAC catalog truncates an MD5 digest to 16 hexadecimal characters, then uses that 64-bit value as the key for a privilege subtree. Exploitation requires low-privileged local access, authorization enabled, and a crafted collision; a victim role then resolves donor permissions.

CVSS severity7.0
High
EPSS probability0.09%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Weak hashing in Milvus 2.6.0 through 2.6.13 allows local users to inherit another role's privileges through a grantee-ID collision. The RBAC catalog truncates an MD5 digest to 16 hexadecimal characters, then uses that 64-bit value as the key for a privilege subtree. Exploitation requires low-privileged local access, authorization enabled, and a crafted collision; a victim role then resolves donor permissions.

The record

CVE
CVE-2026-10814
Published
Jun 4, 2026
Updated
Jun 4, 2026
Vendor
Milvus
Product
Milvus
Classifications
CWE-328, CWE-327, T1068
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Jun 4, 2026CVE publishedPublication date reported by the CVE source.
  2. Jun 4, 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=2.6.0
  2. Affected versionversion=2.6.1
  3. Affected versionversion=2.6.10
  4. Affected versionversion=2.6.11
  5. Affected versionversion=2.6.12
  6. Affected versionversion=2.6.13
  7. Affected versionversion=2.6.2
  8. Affected versionversion=2.6.3
  9. Affected versionversion=2.6.4
  10. Affected versionversion=2.6.5
  11. Affected versionversion=2.6.6
  12. Affected versionversion=2.6.7
  13. Affected versionversion=2.6.8
  14. Affected versionversion=2.6.9

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

Milvus · Milvusversion=2.6.0; version=2.6.1; version=2.6.10; version=2.6.11; version=2.6.12; version=2.6.13; version=2.6.2; version=2.6.3; version=2.6.4; version=2.6.5; version=2.6.6; version=2.6.7; version=2.6.8; version=2.6.9

Published CVSS scores

3.5VulDBAV:L/AC:H/Au:S/C:P/I:P/A:P
1.1VulDBCVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P
4.5VulDBCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L
7.0NVDCVSS:3.1/AV:L/AC:H/PR:L/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)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-328Use of Weak Hash
CWE-327Use of a Broken or Risky Cryptographic Algorithm
T1068Exploitation for Privilege Escalation

Public exploit references

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