https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 18 Oct 2026 03:23:34 +0000 https://cve.radiocsirt.org/vuln/cve-2026-60090 <p><strong>Affected:</strong> MervinPraison PraisonAI</p> <p>PraisonAI before 4.6.78 fails to validate the caller-controlled dimension argument in the PGVector and Cassandra knowledge-store create_collection() backends. Although schema, keyspace, and collection-name identifiers are validated, the dimension value (declared as int but not enforced at runtime) is interpolated directly into the vector column of the generated CREATE TABLE DDL. A caller able to influence collection-creation dimensions can pass a string such as &#39;3); DROP TABLE tenant_secrets; --&#39; to inject SQL/CQL tokens into the statement executed by the database driver.</p> <p><strong>Affected:</strong> MervinPraison PraisonAI</p> <p>PraisonAI before 4.6.78 fails to validate the caller-controlled dimension argument in the PGVector and Cassandra knowledge-store create_collection() backends. Although schema, keyspace, and collection-name identifiers are validated, the dimension value (declared as int but not enforced at runtime) is interpolated directly into the vector column of the generated CREATE TABLE DDL. A caller able to influence collection-creation dimensions can pass a string such as &#39;3); DROP TABLE tenant_secrets; --&#39; to inject SQL/CQL tokens into the statement executed by the database driver.</p> https://cve.radiocsirt.org/vuln/cve-2026-60090 https://cve.radiocsirt.org/vuln/ghsa-wf65-4jjx-q444 <p><strong>Affected:</strong> PyPI: praisonai</p> <p># PGVector and Cassandra knowledge stores interpolate vector dimensions into DDL</p> <p>## Summary</p> <p>The PGVector and Cassandra knowledge-store backends validate SQL/CQL identifiers such as schema, keyspace, and collection names, but still insert the caller-controlled `dimension` argument directly into `CREATE TABLE` vector column declarations. A caller that can influence collection creation dimensions can append SQL/CQL tokens to the generated DDL executed by the database driver.</p> <p>## Technical Details</p> <p>The affected boundary is the vector-store collection creation API. The shared `KnowledgeStore.create_collection()` contract declares `dimension: int`, but Python type hints are not enforced at runtime. Backends that interpolate that value into DDL must validate the runtime value before constructing SQL/CQL.</p> <p>`src/praisonai/praisonai/persistence/knowledge/pgvector.py` already treats DDL identifier interpolation as security-sensitive: `__init__()` calls `validate_identifier(schema, name=&#34;schema&#34;)`, and `_table_name()` calls `validate_identifier(collection, name=&#34;collection name&#34;)` before returning `f&#34;{self.schema}.praison_vec_{collection}&#34;`. However, `PGVectorKnowledgeStore.create_collection()` then executes:</p> <p>```python cur.execute(f&#34;&#34;&#34; CREATE TABLE IF NOT EXISTS {table} ( id VARCHAR(255) PRIMARY KEY, content TEXT, content_hash VARCHAR(64), created_at DOUBLE PRECISION, metadata JSONB, embedding vector({dimension}) ) &#34;&#34;&#34;) ```</p> <p>No…</p> <p><strong>Affected:</strong> PyPI: praisonai</p> <p># PGVector and Cassandra knowledge stores interpolate vector dimensions into DDL</p> <p>## Summary</p> <p>The PGVector and Cassandra knowledge-store backends validate SQL/CQL identifiers such as schema, keyspace, and collection names, but still insert the caller-controlled `dimension` argument directly into `CREATE TABLE` vector column declarations. A caller that can influence collection creation dimensions can append SQL/CQL tokens to the generated DDL executed by the database driver.</p> <p>## Technical Details</p> <p>The affected boundary is the vector-store collection creation API. The shared `KnowledgeStore.create_collection()` contract declares `dimension: int`, but Python type hints are not enforced at runtime. Backends that interpolate that value into DDL must validate the runtime value before constructing SQL/CQL.</p> <p>`src/praisonai/praisonai/persistence/knowledge/pgvector.py` already treats DDL identifier interpolation as security-sensitive: `__init__()` calls `validate_identifier(schema, name=&#34;schema&#34;)`, and `_table_name()` calls `validate_identifier(collection, name=&#34;collection name&#34;)` before returning `f&#34;{self.schema}.praison_vec_{collection}&#34;`. However, `PGVectorKnowledgeStore.create_collection()` then executes:</p> <p>```python cur.execute(f&#34;&#34;&#34; CREATE TABLE IF NOT EXISTS {table} ( id VARCHAR(255) PRIMARY KEY, content TEXT, content_hash VARCHAR(64), created_at DOUBLE PRECISION, metadata JSONB, embedding vector({dimension}) ) &#34;&#34;&#34;) ```</p> <p>No…</p> https://cve.radiocsirt.org/vuln/ghsa-wf65-4jjx-q444