vectordb: hardening pgvector provider against potential SQL injection#541
Merged
DoganK01 merged 1 commit intoUpsonic:masterfrom Mar 17, 2026
Merged
Conversation
Member
|
Appreciate the contribution :) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Added Pydantic validation for table and schema names in PgVectorConfig to ensure they only contain alphanumeric characters and underscores. Additionally, I updated the PgVector provider to use double quotes for all DDL statements (CREATE SCHEMA, CREATE INDEX) involving user-supplied identifiers. While these values usually come from configuration, these changes provide an important layer of defense when collection names are dynamically generated by agents.