Case · DiggingBeagle record

HNSW hub-and-satellite poisoned documents redirect RAG answer evidence

Attacker-inserted hub and satellite documents exploit HNSW graph navigation and falsely anchored claims to influence answers to previously unseen queries.

Scope

arXiv:2610.21464, synthetic/controlled HNSW RAG retrieval experiments; index modification adversary.

Assessment profile

Assessment method
Setting
simulation
Exploitation
demonstrated
Evidence
Grade B
Remediation
mitigation available
AI role
AGAINST AI
Basis and provenance

The directly inspected HNSW RAG study describes an insertion-only attacker, hub/satellite ablations and two-million-document synthetic controlled retrieval. These data support the reported retrieval and answer effects in that corpus. They do not identify a compromised production search service or show attacker-controlled graph edge edits. Scope and realized impact remain unproven.

Assessed Oct 18, 2026 using diggingbeagle.assessment/1.

At a glance

Mechanism and trust boundary

  1. 01

    Step

  2. 02

    Step

  3. 03

    Step

  4. 04

    Step

Claims & evidence

CLM-CP13-HNSW-MECHANISMInserting crafted hub and satellite poison documents exploits HNSW neighbor topology and increases the chance these adversarial documents are retrieved under unseen topic questions.supported

Basis: reported finding

Link to claim
CLM-CP13-HNSW-CONTROLLEDWith up to 60 injected hub/satellite documents against a two-million-document Wikipedia corpus, the paper reports up to 31.29% answer attack success in selected evaluation settings, not in production.supported

Basis: reported finding

Link to claim
CLM-ENRICH-HNSW-TOPOLOGY-ABLATIONWith 60 injected documents and a tight search budget, the study reports about 8.56 additional percentage points of HNSW-specific retrieval success over the comparable semantic-only effect; that incremental advantage shrinks at higher search budgets.supported

Basis: reported finding

Link to claim

Implications

A retrieval index can give one attacker-controlled claim wider query reach than its individual document similarity suggests. If the answer generator treats retrieved material as evidence without checking origin, the failure is source promotion, not necessarily instruction following. Stronger retrieval depth can reduce some topology gain but cannot authenticate false content.

Controls and mitigations

  • Bind ingestion identity and document provenance to retrievable passages, and compare suspicious results under alternative exact or high-budget retrieval where feasible.
  • Evaluate poisoning controls for false removal of legitimate passages and for answer-level evidence validity, not solely whether a detector finds abnormal embeddings.

Unknowns and contradictions

  • How independent production systems validate index edges and insertion history is unmeasured.
  • The controlled corpus results do not prove intrusion into a live knowledge service.

Sources and citation

Material revision history

  1. Oct 18, 2026 · Canonical change recorded · new in release · revision 171