Unauthenticated API access via default NoAuth backend
Published Apr 25, 2026 · Updated Apr 25, 2026
Missing authentication in Vanna 2.0.0 through 2.0.2 allows remote attackers to access legacy Flask API endpoints without credentials. VannaFlaskApp defaults its authentication backend to NoAuth, whose login check accepts every request before protected /api/v0 routes run. A network-reachable legacy Flask deployment using the default backend exposes configuration and data operations, including SQL execution and training-data changes.
Summary
What happened
Missing authentication in Vanna 2.0.0 through 2.0.2 allows remote attackers to access legacy Flask API endpoints without credentials. VannaFlaskApp defaults its authentication backend to NoAuth, whose login check accepts every request before protected /api/v0 routes run. A network-reachable legacy Flask deployment using the default backend exposes configuration and data operations, including SQL execution and training-data changes.
The record
- CVE
- CVE-2026-6977
- Published
- Apr 25, 2026
- Updated
- Apr 25, 2026
- Vendor
- Vanna AI
- Product
- Vanna
- Classifications
- CWE-266, CWE-285, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 25, 2026CVE publishedPublication date reported by the CVE source.
- Apr 25, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.0.0
- Affected versionversion=2.0.1
- Affected versionversion=2.0.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Unauthenticated legacy Flask API proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo