CVE-2025-15453 milvus HTTP Endpoint expr.go expr.Exec deserialization
Medium 5.3
Published
Updated
Check this codebase for CVE-2025-15453 and fix it if it is affected.
What it is: CVE-2025-15453 is a medium-severity vulnerability in milvus, published on 5 Jan 2026.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-15453 exists.
Affected product: milvus. 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-2025-15453/ (Markdown: https://insights.sbomify.com/CVE-2025-15453/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2025-15453?
CVE-2025-15453 is a medium-severity vulnerability in milvus, published on 5 Jan 2026.
Official description
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.
Which versions are affected by CVE-2025-15453?
How do I fix CVE-2025-15453?
No fix has been published for CVE-2025-15453 yet. Limit exposure of the affected software until one is available.
Is CVE-2025-15453 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-15453 exists.
Sources
Also known as GHSA-2wmv-mm4p-p4mx.