Browse / Sensitive Data Disclosure / Information exposure
Information exposure
23 records in Sensitive Data Disclosure.
- Mem0: Cross-tenant conversation leak via unescaped delimiter collision in session-scope key (_build_session_scope) Conversation scope keys join caller-supplied identifiers with unescaped delimiters, so a crafted run_id can match another tenant's stored messages.
- MLflow CrewAI autologging records LLM provider API keys in logged trace spans
- Pydantic AI OpenTelemetry instrumentation: retry prompt content is not redacted when `include_content=False` Retry prompts without tool calls are written to telemetry spans even when content redaction is enabled, so withheld model content reaches the observability backend.
- Pydantic AI OpenTelemetry instrumentation: exception events on tool and agent run spans include content when `include_content=False` Exception events and error statuses on agent spans carry prompts, tool arguments and provider responses even when content export is disabled.
- vLLM: Harmony tool continuations drop `cache_salt` — restoring a cross-tenant prefix-cache membership oracle Tool continuation turns are cached without the tenant's cache salt, so another tenant can infer guessed prompts from exact cached-token counts.
- Open WebUI: A user's session cookies are sent to tool servers configured for bearer authentication
- Flowise: Information Disclosure in GET /api/v1/upsert-history returns the entire server-wide upsert history The upsert history endpoint returns every workspace's ingestion records without scoping, exposing vector store endpoints and collection names.
- Flowise: Incomplete Credential Redaction Exposes Secrets via API
- Open WebUI: /api/v1/channels/{id}/members exposes full user model including sensitive credentials
- n8n: Custom Header Credential Values Leaked in Plaintext into LLM Node Execution Data Custom header values from LLM node credentials are stored in plaintext in workflow execution data, where users with execution access can read them.
- n8n: Google Service Account Private Key Exposed in JWT Header The full service account private key was written into the JWT header's key ID field, so anyone who can read those headers can recover it.
- n8n: SecurityScorecard Node Leaks API Token to User-Controlled Host
- FlowiseAI Vulnerable to Credential Data Leak Credential lookups with a name filter return the encrypted data field, which the unfiltered path strips, exposing stored API secrets.
- FlowiseAI Exposes Basic Auth Credentials via API
- Flowise: Bcrypt Password Hash Exposure The Flowise login handler returns bcrypt password hashes in its response, so a remote caller can obtain other users' hashes.
- Langflow has an Information Leak through Incomplete API Key Redaction API key redaction in flow handling misses some cases, so stored credentials are returned to remote callers.
- Flowise: Public chatflow endpoints return unsanitized flowData including plaintext API keys, passwords, and credential IDs
- Flowise: Sensitive Data Leak in public-chatbotConfig An unauthenticated endpoint returns full chatflow configuration, including stored API keys and authorization headers, to anyone who knows a chatflow ID.
- Gradio: Mocked OAuth Login Exposes Server Credentials and Uses Hardcoded Session Secret
- Claude Code Leaks Data via Malicious Environment Configuration Before Trust Confirmation
- Potential Timing Side-Channel Vulnerability in vLLM’s Chunk-Based Prefix Caching Response timing differs when a prompt prefix is already cached, so a co-tenant can infer whether a guessed prompt matches a victim's.
- LiteLLM Has a Leakage of Langfuse API Keys An error path while parsing team settings exposes the Langfuse secret and public keys in output.
- Update share links to use FRP instead of SSH tunneling The share link tunnel sends a private SSH key to connecting clients, which lets them reach other users' shared demos.