CVE-2026-4231
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 · uneditedA vulnerability was found in vanna-ai vanna up to 2.0.2. Affected by this vulnerability is the function update_sql/run_sql of the file src/vanna/legacy/flask/__init__.py of the component Endpoint. Performing a manipulation results in server-side request forgery. The attack may be initiated remotely. The exploit has been made public and could 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 confidenceServer-Side Request Forgery (SSRF) vulnerability in vanna-ai versions up to 2.0.2 in the Flask endpoint functions update_sql/run_sql within src/vanna/legacy/flask/__init__.py. The endpoint accepts user-controlled URLs without proper validation, allowing remote attackers to force the server to make requests to arbitrary internal or external resources.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify vanna-ai versionRun `pip show vanna` or check your requirements.txt/package-lock.json for the installed version of vanna-aiAffected if The installed version is 2.0.2 or lower, or any version up to and including 2.0.2 (e.g., 2.0.0, 1.x.x)
-
Locate the vulnerable Flask moduleCheck if the file src/vanna/legacy/flask/__init__.py exists in your vanna installation (look in your venv or site-packages directory)Affected if The file src/vanna/legacy/flask/__init__.py exists in your installation
-
Verify update_sql/run_sql functions are exposedInspect the Flask __init__.py file and look for route decorators exposing update_sql or run_sql functions, or check your Flask app routing configuration for these endpointsAffected if The Flask application has routes defined for update_sql or run_sql endpoints without authentication guards
-
Confirm lack of URL validationExamine the source code of the update_sql and run_sql functions in src/vanna/legacy/flask/__init__.py to see if user-supplied URL parameters are passed directly to request libraries without validationAffected if The code accepts URL parameters and makes requests without validating the URL against an allowlist or restricting destinations
-
Check endpoint accessibilityDetermine if the update_sql/run_sql endpoints are accessible to unauthenticated users by reviewing your Flask app configuration, authentication middleware, or proxy settingsAffected if The endpoints are accessible to unauthenticated or untrusted users on your network
You are affected if you are running vanna-ai version 2.0.2 or lower, have the legacy Flask module loaded, and the update_sql/run_sql endpoints are exposed without authentication or URL validation.
Generated from the published advisory. Verify against your own configuration.
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 dataRestrict the update_sql/run_sql endpoints to authenticated users only and implement strict URL allowlisting to limit requests to trusted destinations, preventing attackers from abusing the endpoint for SSRF attacks against internal infrastructure.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2026-4231 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-4231 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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