dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2025-15453

MEDIUM · 6.3 CVSS v3.1 Published 2026-01-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A security vulnerability has been detected in milvus up to 2.6.7. This vulnerability affects the function expr.Exec of the file pkg/util/expr/expr.go of the component HTTP Endpoint. The manipulation of the argument code leads to deserialization. Remote exploitation of the attack is possible. The exploit has been disclosed publicly and may be used. A fix is planned for the next release 2.6.8.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A deserialization vulnerability exists in the expr.Exec function in pkg/util/expr/expr.go of the Milvus HTTP Endpoint. The code argument is processed through unsafe deserialization, allowing remote attackers to potentially execute arbitrary code by crafting malicious input.

MitigationUpgrade to Milvus 2.6.8 when released. Until then, restrict network access to the HTTP endpoint and implement firewall rules to limit exposure to untrusted users.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Milvus installation and version
    Run 'milvus --version' or check the running Milvus service version through the API or container tag
    Affected if Milvus version is lower than 2.6.8 (the fixed version)
  2. Verify HTTP endpoint is enabled
    Check Milvus configuration files (typically in etcd or config map) for HTTP endpoint settings; look for 'http' or 'restful' in enabled services
    Affected if HTTP endpoint is exposed and accessible over network
  3. Confirm expr.Exec function is reachable
    Inspect the Milvus deployment to determine if the expression evaluation feature is in use; this is typically used in query/filter operations
    Affected if The expression/filter feature is enabled and processing user-controlled input through the code parameter
  4. Check network exposure of HTTP port
    Review firewall rules, network policies, and service definitions to determine if port 9091 (default Milvus HTTP) is exposed to untrusted networks
    Affected if HTTP endpoint is accessible from untrusted network segments

A user is affected if running a Milvus version below 2.6.8 with the HTTP endpoint enabled and exposed to network traffic that could send malicious code to the expr.Exec function.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Milvus 2.6.8 when released. Until then, restrict network access to the HTTP endpoint and implement firewall rules to limit exposure to untrusted users.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-15453 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-15453 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data