Skip to main content
VulnerabilityPublished Updated

CVE-2024-5827: vanna-ai/vanna · SQL Injection

Affects vanna-ai/vannaSource CVE Database V5

0

Not known to be exploited · public detection template (Nuclei) · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 15:59 UTC

CVSS 3.0 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
3.4% chance of exploitation in 30 days – higher than 88% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Jun 2024

  2. Detectable: evidence found.

    nuclei template: Vanna - SQL injection

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubvanna-ai/vannapkg:github/vanna-ai/vannaOther threatsAffected
  • =0.3.4
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  1. Immediately restrict network access to the vanna-ai Flask API endpoints, limiting exposure to trusted internal networks or VPNs.
  2. Implement strict input validation and sanitization on all SQL training data inputs to prevent injection of malicious SQL commands.
  3. Monitor file system changes on servers running vanna-ai for unauthorized file creation, especially suspicious PHP or script files.
  4. Deploy Web Application Firewalls (WAFs) with rules targeting SQL injection patterns specific to DuckDB and Flask API traffic.
  5. Conduct thorough code reviews and security testing on the DuckDB integration layer to identify and fix injection points.
  6. Apply patches or updates from the vendor as soon as they become available.
  7. Employ runtime application self-protection (RASP) tools to detect and block injection attempts in real time.
  8. Educate development and operations teams about secure coding practices related to SQL injection and API security.
  9. Use network segmentation to isolate AI infrastructure from critical business systems to limit lateral movement in case of compromise.
  10. Prepare incident response plans specifically addressing web API compromises and backdoor detection.

Description

Vanna v0.3.4 is vulnerable to SQL injection in its DuckDB integration exposed to its Flask Web APIs. Attackers can inject malicious SQL training data and generate corresponding queries to write arbitrary files on the victim's file system, such as backdoor.php with contents `<?php system($_GET[0]); ?>`. This can lead to command execution or the creation of backdoors.

References

Community reviews

Loading reviews…