How to fix: Pinecone API key in source
Pinecone keys grant vector-DB control.
Why it matters
An exposed Pinecone API key grants full control over your vector database: an attacker can delete all vectors (destroying your semantic search), upsert poisoned embeddings, query all indexed data, or create new indexes at your expense.
Pinecone keys grant vector-DB control.
How to fix it
- 1Rotate the key in the Pinecone console under API Keys
- 2Keep Pinecone API calls server-side only; never expose the key in browser bundles
- 3Use environment-scoped keys when available
Code examples
Server-only Pinecone client
// Only call Pinecone from server-side API routes: never from client components
import { Pinecone } from '@pinecone-database/pinecone';
const pc = new Pinecone({
apiKey: process.env.PINECONE_API_KEY!, // server-only env var
});References
Detected automatically by VulnRadar. The check id is secret-pinecone-api-key, stable across every scan so you can filter or diff on it.
More secrets checks
Questions
- How severe is Pinecone API key in source?
- VulnRadar rates this high severity in the secrets category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id secret-pinecone-api-key, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Pinecone API key in source map to?
- It maps to CWE-798. In the OWASP Top 10 it falls under A07:2021.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.