dbcve.org
InjectionWeakness · CWE-74

CVE-2026-4230

MEDIUM · 6.3 CVSS v3.1 Published 2026-03-16
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 has been found in vanna-ai vanna up to 2.0.2. Affected is the function update_sql of the file src/vanna/legacy/flask/__init__.py of the component Endpoint. Such manipulation leads to sql injection. The attack can be launched remotely. The exploit has been disclosed to the 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 · high confidence

SQL injection vulnerability in the update_sql function within src/vanna/legacy/flask/__init__.py of vanna-ai up to version 2.0.2. The endpoint accepts user-supplied input that is directly concatenated into SQL queries without proper parameterization or sanitization, allowing remote attackers to manipulate SQL statements.

MitigationImplement parameterized queries (prepared statements) for all SQL operations in the update_sql function and apply input validation/sanitization. Until vendor patch is available, restrict network access to the affected endpoint and monitor for exploitation attempts.

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. Identify installed vanna-ai version
    Run 'pip show vanna' or check your dependency lock file for the vanna package version
    Affected if Version is 2.0.2 or lower
  2. Locate the vulnerable file
    Check if src/vanna/legacy/flask/__init__.py exists in your vanna installation directory
    Affected if The legacy flask module file is present in your environment
  3. Determine if legacy flask endpoint is exposed
    Inspect your Flask application's routing configuration to see if any routes import or reference the legacy flask module from vanna. Check for endpoints that may map to update_sql functionality
    Affected if The legacy/flask module routes are registered and accessible in your application
  4. Check if update_sql is callable
    Review your application code for any HTTP endpoints or internal calls to the update_sql function within the legacy flask module
    Affected if The update_sql function can be invoked via HTTP request or internal application logic

You are affected if you are running vanna-ai version 2.0.2 or lower and your application exposes or uses the legacy flask module with the update_sql function accessible to untrusted input.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement parameterized queries (prepared statements) for all SQL operations in the update_sql function and apply input validation/sanitization. Until vendor patch is available, restrict network access to the affected endpoint and monitor for exploitation attempts.

Recommended fix Moderate confidence

latest stable vanna-ai release (version higher than 2.0.2)

  1. 1. Identify the current installed version of vanna-ai in your environment by checking your requirements.txt, setup.py, or running pip show vanna
  2. 2. If running vanna-ai version 2.0.2 or below, upgrade to the latest stable release that addresses this SQL injection vulnerability
  3. 3. After upgrading, verify the src/vanna/legacy/flask/__init__.py file has been updated, specifically reviewing the update_sql function for proper parameterized queries or input sanitization
  4. 4. Test the update_sql endpoint functionality to ensure legitimate operations still work correctly
  5. 5. Review application logs for any attempted SQL injection exploits targeting this endpoint
Caveat legacy Flask endpoints may be deprecated or restructured; verify compatibility with existing integrations using the Flask API

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-4230 — 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-4230 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