CVE-2024-3829 is a critical severity vulnerability (CVSS 9.1) in Qdrant. Snapshot recovery can be abused with symlinks to read and write arbitrary files on the server, which could lead to full takeover. The record says the issue is fixed in version v1.9.0.
What's affected
- qdrant/qdrant version 1.9.0-dev, according to the record.
Severity in the record: Critical, CVSS 9.1, vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N. In plain terms: over the network, no privileges required, no user interaction. Weakness class: CWE-59, improper link resolution before file access.
Fixed version: The record says the issue is fixed in version v1.9.0. A commit and a huntr report are listed as references.
The record's KEV flag is false, so this CVE is not in the CISA Known Exploited Vulnerabilities catalog, and no source reviewed here reports exploitation in the wild.
How to check if you're exposed
- Ask a running server for its version:
curl http://localhost:6333/. - For containers, check the image tag:
docker ps --format '{{.Image}}' | grep qdrant. - In a Python project, check the client only if you also run the server locally:
pip show qdrant-client.
You can also paste a dependency manifest into the free in-browser dependency scan to see which known CVEs your libraries carry. That helps for packages such as Pydantic or Qdrant clients, while self-hosted applications are best tracked in an inventory by hand.
What to do now
- Upgrade to the fixed release.
- Only recover snapshots from sources you created and trust.
- Restrict who can reach the snapshot recovery interface of the service.
- Record the decision in your tracker with the CVE id and the date, so the next audit can see what you did about CVE-2024-3829.
Why it matters
A symbolic link is a file that points at another file. If code unpacks an archive and then reads or writes through entries without checking where links lead, an archive can steer the operation to a path outside the intended directory. Safe extraction rejects links, or resolves each target and verifies it stays inside the destination.
A snapshot is an archive of a collection that Qdrant can restore. If the archive includes a link pointing at a file outside the intended folder, the recovery process can read or write that target. The record says writing a payload file next to a link gives arbitrary file write, which is why the score is 9.1. Only restore snapshots you made yourself or got from a source you trust.
Look up the entry on Gold to see how it connects to other advisories, and use reachability analysis to separate the components that actually call vulnerable code from the ones that merely sit in your inventory.
Try it yourself
Click through it at your own pace, or open it full screen.
Quick check
Is 1.9.0-dev a release I would have installed?
It is a development version string. Production installs normally run a tagged release, so check whether you ever ran a build from the main branch.
Is CVE-2024-3829 in the CISA KEV catalog?
No. The record's KEV flag is false.
Sources
These links come from the NVD record. They were not retrievable when this post was written, so the details above rest on the record text. Check them before you act.
Last reviewed: 19 October 2026.
