Update Code#72
Closed
pineconemachine wants to merge 1 commit into
Closed
Conversation
jhamon
added a commit
that referenced
this pull request
Feb 3, 2026
Fixed security vulnerability (CWE-312, CWE-532) where API key response objects containing sensitive data were being logged. Now only logging non-sensitive IDs instead of full response objects. Resolves code scanning alert #72 Co-authored-by: Cursor <cursoragent@cursor.com>
jhamon
added a commit
that referenced
this pull request
Feb 3, 2026
Fixed security vulnerability (CWE-312, CWE-532) where API key response objects containing sensitive data were being logged. Now only logging non-sensitive IDs instead of full response objects. Resolves code scanning alert #72 Co-authored-by: Cursor <cursoragent@cursor.com>
jhamon
added a commit
that referenced
this pull request
Feb 3, 2026
## Summary Fixed security vulnerability where API key response objects containing sensitive data were being logged in clear text in test files. ## Changes - Modified `tests/integration/rest_sync/admin/test_api_key.py` to log only non-sensitive API key IDs instead of full response objects - This prevents exposure of sensitive data (passwords/API key values) in logs ## Security Impact - Resolves code scanning alert #72: https://github.com/pinecone-io/pinecone-python-client/security/code-scanning/72 - Addresses CWE-312 (Cleartext Storage of Sensitive Information) - Addresses CWE-532 (Insertion of Sensitive Information into Log File) - Security severity: High ## Testing - Existing tests continue to pass - Pre-commit hooks passed Made with [Cursor](https://cursor.com) <!-- CURSOR_SUMMARY --> --- > [!NOTE] > **Low Risk** > Low risk test-only change that reduces exposure of sensitive API key material in logs; no runtime behavior is affected. > > **Overview** > Updates the admin API key integration test to **stop logging full API key response objects** and instead log only non-sensitive identifiers (the key `id`) when fetching via `fetch`/`get` aliases, preventing accidental leakage of API key values in test logs. > > <sup>Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit a5cf44f. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).</sup> <!-- /CURSOR_SUMMARY --> Co-authored-by: Cursor <cursoragent@cursor.com>
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.
Update generated code from latest proto defintions