CVE-2026-40315
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 · uneditedPraisonAI is a multi-agent teams system. Prior to 4.5.133, there is an SQL identifier injection vulnerability in SQLiteConversationStore where the table_prefix configuration value is directly concatenated into SQL queries via f-strings without any validation or sanitization. Since SQL identifiers cannot be safely parameterized, an attacker who controls the table_prefix value (e.g., through from_yaml or from_dict configuration input) can inject arbitrary SQL fragments that alter query structure. This enables unauthorized data access, such as reading internal SQLite tables like sqlite_master, and manipulation of query results through techniques like UNION-based injection. The vulnerability propagates from configuration input in config.py, through factory.py, to the SQL query construction in sqlite.py. Exploitation requires the ability to influence configuration input, and successful exploitation leads to internal schema disclosure and full query result tampering. This issue has been fixed in version 4.5.133.
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 confidenceSQL identifier injection vulnerability in PraisonAI's SQLiteConversationStore where the table_prefix configuration value is directly concatenated into SQL queries via f-strings without validation. Since SQL identifiers cannot be parameterized like regular values, an attacker controlling table_prefix through from_yaml or from_dict can inject arbitrary SQL fragments, enabling reading internal SQLite tables like sqlite_master and UNION-based injection for data exfiltration or query manipulation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 4.5.133CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
-
Check installed PraisonAI versionRun: pip show praisonai or pip show praisonai and note the Version fieldAffected if Version is lower than 4.5.133 (e.g., 4.5.0, 4.4.x, etc.)
-
Locate SQLiteConversationStore usageSearch codebase for imports of SQLiteConversationStore or look in the project for files that instantiate conversation storage with SQLiteConversationStoreAffected if SQLiteConversationStore is imported and used in the application code
-
Identify table_prefix configuration sourceSearch for from_yaml or from_dict calls that load configuration containing table_prefix, or grep for 'table_prefix' in config files and YAML filesAffected if table_prefix is configurable via YAML or dictionary loading (from_yaml/from_dict)
-
Inspect table_prefix value in code or configReview configuration files or runtime code where table_prefix is set; look for values that could contain SQL characters like quotes, semicolons, UNION, SELECT, etc.Affected if table_prefix allows non-alphanumeric characters beyond underscores (e.g., contains quotes, spaces, SQL keywords)
-
Verify SQL query construction methodExamine the SQLiteConversationStore source code (typically in a stores/ or db/ directory) for f-string SQL queries that include table_prefix directly, such as f"SELECT * FROM {table_prefix}..."Affected if Code uses f-strings or string concatenation to insert table_prefix into SQL queries without validation
You are affected if running PraisonAI version below 4.5.133 AND using SQLiteConversationStore with table_prefix configured via from_yaml or from_dict, where the prefix value can contain arbitrary characters.
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.
dbcve · scoped4.5.133
Upgrade to version 4.5.133 or later. If unable to upgrade immediately, implement strict whitelist-based validation for table_prefix to ensure only alphanumeric and underscore characters are accepted, preventing any SQL injection through identifier manipulation.
4.5.133
- Check current installed version of PraisonAI (e.g., pip show praisonai or pip list)
- Upgrade PraisonAI to version 4.5.133 or later using: pip install --upgrade praisonai>=4.5.133 or pip install praisonai==4.5.133
- Verify the upgrade was successful by checking the installed version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-40315 — 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-40315 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