Disclosed weakness · no CVE recorded

Dify could delete another dataset’s vectors when attachment identifiers were shared

Dify · Dify · Qdrant vector provider

First documented disclosure · Review checkpoint

Summary

Deleting an attachment identifier in one dataset could remove a surviving vector belonging to another dataset in the same collection.

Severity and exploitation evidence

No CVSS score recorded in this review.

Exploitation not established: The reviewed sources describe a correction or controlled reproduction; malicious exploitation against users is not established.

Exploitation evidence source

Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.

How the weakness works

The delete-by-ID filter used the attachment identifier without the dataset group constraint.

Conditions required

Two datasets share a Qdrant collection and an attachment identifier, and deletion is requested for one dataset.

Potential impact

Vectors outside the target dataset could be deleted, damaging retrieval integrity and availability.

Affected versions and configurations

The reviewed upstream report does not establish a complete affected-release range.

Fix and mitigation status

1.20.0 contains the Qdrant provider correction. The report’s related Relyt and TiDB provider observations are not established fixed by this patch.

Practical next steps

Upgrade to 1.20.0 and assess affected shared collections for unintended vector deletion.

Operating lesson

Bind destructive storage operations to both object identity and tenant or dataset scope.

Evidence and limits

An October 10 inline review identified this specific cross-dataset issue, earlier than the November 4 fix PR. The September document-cleanup report concerns related but different behavior. Tagged verification: delete_by_ids combines document identifiers with the current group_id. The PR tests use the native local Qdrant SDK, not a cloud deployment.

Sources