Security Digest · Vulnerability record

CVE-2024-5565: Vanna prompt injection code execution

The Vanna library uses a prompt function to present the user with visualized results, it is possible to alter the prompt using prompt injection and run arbitrary Python code instead of the intended visualization code.

CVSS 9.2 Critical EPSS 15.2% · p97

Should you act?

High exploit likelihood

EPSS ranks it in the top 5% of all CVEs for likely exploitation in the next 30 days. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.

  • Not in CISA KEV, but CISA’s SSVC assessment records a public proof-of-concept, so attack code exists.
  • EPSS 15.2%, percentile 97: FIRST’s model estimates a 15.2% chance of exploitation activity in the next 30 days, higher than 97% of all scored CVEs (very high). EPSS is a probability, not a verdict.
  • Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
  • Only applies if your dependency tree includes vanna (PyPI) <= 0.5.5, no fixed version listed. Check your lockfile, including transitive dependencies.

What it is

The Vanna library uses a prompt function to present the user with visualized results, it is possible to alter the prompt using prompt injection and run arbitrary Python code instead of the intended visualization code. Specifically - allowing external input to the library’s “ask” method with "visualize" set to True (default behavior) leads to remote code execution.

From the GitHub advisory

The Vanna library uses a prompt function to present the user with visualized results, it is possible to alter the prompt using prompt injection and run arbitrary Python code instead of the intended visualization code. Specifically - allowing external input to the library’s “ask” method with "visualize" set to True (default behavior) leads to remote code execution.

Weakness type: CWE-94, CWE-77.

Product: vanna (PyPI) · Assigned by: JFROG · Published: 2024-05-31

Affected and fixed versions

EcosystemPackageVulnerableFirst fixed
PyPIvanna<= 0.5.5none listed
VendorProductAffected versions (per CVE record)
vanna0

Severity scores

Scored byCVSSScoreVector
JFROG3.18.1 HighCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
GitHub4.09.2 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
  • Attack vector: network (remotely reachable)
  • Attack complexity: low
  • Attack requirements: present (depends on deployment conditions)
  • Privileges required: none (no login)
  • User interaction: none

CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.

Exploitation and urgency

  • CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
  • CISA SSVC assessment: exploitation poc, automatable no, technical impact total.
  • FIRST EPSS (model of 2026-10-21): 15.18% probability of exploitation activity in the next 30 days; percentile 97.

Timeline

  • — CVE record published by JFROG
  • — GitHub-reviewed advisory GHSA-7735-w2jp-gvg6 published (critical)
  • — CVE record last updated

Sources and references

Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.

Vulnerability records

  1. GitHub Advisory GHSA-7735-w2jp-gvg6 github.com
  2. CVE.org record CVE-2024-5565 cve.org
  3. NVD entry CVE-2024-5565 nvd.nist.gov

Other references from the CVE record and advisory

  1. research.jfrog.com research.jfrog.com

Critical PyPI advisories · Today’s Security Digest