dbcve.org
InjectionWeakness · CWE-74

CVE-2026-4513

MEDIUM · 6.3 CVSS v3.1 Published 2026-03-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability was detected in vanna-ai vanna up to 2.0.2. Affected by this vulnerability is the function ask of the file vanna\legacy\base\base.py. Performing a manipulation results in sql injection. The attack is possible to be carried out remotely. The exploit is now public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

SQL injection vulnerability in the ask function of vanna\legacy\base\base.py in vanna-ai vanna up to version 2.0.2 allows remote attackers to inject malicious SQL queries through user-supplied input without proper sanitization or parameterized queries.

MitigationSince the vendor did not respond, assess if a patched version is available; otherwise, implement proper input validation and convert dynamic SQL queries to parameterized queries in the affected function.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed vanna version
    Run 'pip show vanna' or 'pip list | grep vanna' to see the installed version
    Affected if Version is 2.0.2 or below (up to and including 2.0.2)
  2. Locate the vulnerable file
    Find vanna/legacy/base/base.py in your Python environment (run 'python -c "import vanna; print(vanna.__file__)"' to get the base path)
    Affected if The file exists and contains an 'ask' function that processes user input as SQL
  3. Inspect the ask function implementation
    Open vanna/legacy/base/base.py and examine the 'ask' function for direct string concatenation or formatting of SQL queries using user input
    Affected if The function constructs SQL queries by concatenating user-supplied input without using parameterized queries or proper escaping
  4. Determine if legacy module is in use
    Search your codebase for imports like 'from vanna.legacy import VannaBase' or direct usage of the legacy module
    Affected if Your application imports or uses the vanna.legacy module which contains the vulnerable code
  5. Check for user input exposure to ask function
    Review your application code that calls the 'ask' function and trace whether web forms, API parameters, or other user-controllable data are passed as the SQL question input
    Affected if User-supplied input flows directly to the ask function without validation

You are affected if you are using vanna version 2.0.2 or lower, your code imports from vanna.legacy, and user input reaches the ask function without validation or parameterized query usage.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Since the vendor did not respond, assess if a patched version is available; otherwise, implement proper input validation and convert dynamic SQL queries to parameterized queries in the affected function.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-4513 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-4513 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data