CVE-2026-41219 is a medium severity vulnerability in F5 BIG-IP's QKView utility where improper sanitization allows a low-privileged attacker to read sensitive information from a QKView file. This issue affects versions 16.1.0, 17.1.0, and 17.5.0. The vulnerability does not impact integrity or availability but compromises confidentiality. No official patch or remediation guidance is currently provided, and no known exploits are reported in the wild.
When schema validation is enabled on a collection and an update or insert would violate the collection's schema, the local server log message generated may not have all user data redacted.
This issue impacts MongoDB Server v7.0 versions prior to 7.0.34, v8.0 versions prior to 8.0.23, v8.2 versions prior to 8.2.9 and v8.3 versions prior to 8.3.2.
JunoClaw is an agentic AI platform built on Juno Network. Prior to 0.x.y-security-1, every MCP write tool (send_tokens, execute_contract, instantiate_contract, upload_wasm, ibc_transfer, etc.) accepted 'mnemonic: string' as an explicit tool-call parameter. The BIP-39 seed was consequently embedded in the LLM tool-call JSON, exposing it to any transport, log, or telemetry surface in the path between the LLM provider and the MCP process. This vulnerability is fixed in 0.x.y-security-1.
CVE-2026-41018 is a vulnerability in the Apache Airflow Providers Elasticsearch logging integration where credentials embedded in the Elasticsearch host URL are written in full to task logs. This exposure allows any user with permission to read task logs to access sensitive backend credentials. The vulnerability has a medium severity with a CVSS score of 6.5. Users are advised to upgrade to version 6.5.3 or later and to avoid embedding credentials directly in the host URL by using a secret backend configuration instead.
Apache Airflow Providers OpenSearch versions prior to 1.9.1 log the full host URL including embedded credentials in task logs when configured with a host URL containing credentials. This allows any user with task-log read permission to access sensitive backend credentials. The vulnerability is classified as CWE-532 (Insertion of Sensitive Information into Log File). Users are advised to upgrade to version 1.9.1 or later and to configure backend credentials using a secret backend rather than embedding them in the host URL as a defense-in-depth measure.
### Impact
When `n8n-mcp` runs in HTTP transport mode, authenticated MCP `tools/call` requests had their full arguments and JSON-RPC params written to server logs by the request dispatcher and several sibling code paths before any redaction. When a tool call carries credential material — most notably `n8n_manage_credentials.data` — the raw values can be persisted in logs.
In deployments where logs are collected, forwarded to external systems, or viewable outside the request trust boundary (shared log storage, SIEM pipelines, support/ops access), this can result in disclosure of:
- bearer tokens and OAuth credentials sent through `n8n_manage_credentials`
- per-tenant API keys and webhook auth headers embedded in tool arguments
- arbitrary secret-bearing payloads passed to any MCP tool
The issue requires authentication (`AUTH_TOKEN` accepted by the server), so unauthenticated callers cannot trigger it; the runtime exposure is also reduced by an existing console-silencing layer in HTTP mode, but that layer is fragile and the values are still constructed and passed into the logger. The fix removes the leak at the source.
Impact category: **CWE-532** (Insertion of Sensitive Information into Log File). CVSS 3.1 score: **4.3 Medium** (`AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`).
### Affected
Deployments running n8n-mcp **v2.47.12 or earlier** in HTTP transport mode (`MCP_MODE=http`). The stdio transport short-circuits the relevant log calls and is not affected in practice.
### Patched
**v2.47.13** and later.
- npm: `npx n8n-mcp@latest` (or pin to `>= 2.47.13`)
- Docker: `docker pull ghcr.io/czlonkowski/n8n-mcp:latest`
The patch routes tool-call arguments through a metadata-only summarizer (`summarizeToolCallArgs`) that records type, top-level key names, and approximate size — never values. The same pattern was adopted earlier for HTTP request bodies in GHSA-pfm2-2mhg-8wpx.
### Workarounds
If developers cannot upgrade immediately:
- Restrict access to the HTTP port (firewall, reverse proxy, or VPN) so only trusted clients can authenticate.
- Restrict access to server logs (no shared SIEM ingestion, no support read-only access) until the upgrade lands.
- Switch to stdio transport (`MCP_MODE=stdio`, the default for CLI invocation), which has no HTTP surface and short-circuits the affected log calls.
### Credit
n8n-MCP thanks [@Mirr2](https://github.com/Mirr2) (Organization / Jormungandr) for reporting this issue.
### Impact
When `n8n-mcp` runs in HTTP transport mode, incoming requests to the `POST /mcp` endpoint had their request metadata written to server logs regardless of the authentication outcome. In deployments where logs are collected, forwarded to external systems, or viewable outside the request trust boundary (shared log storage, SIEM pipelines, support/ops access), this can result in disclosure of:
- bearer tokens from the `Authorization` header
- per-tenant API keys from the `x-n8n-key` header in multi-tenant setups
- JSON-RPC request payloads sent to the MCP endpoint
Access control itself was not bypassed — unauthenticated requests were correctly rejected with `401 Unauthorized` — but sensitive values from those rejected requests could still be persisted in logs.
Impact category: **CWE-532** (Insertion of Sensitive Information into Log File).
### Affected
Deployments running n8n-mcp **v2.47.10 or earlier** in HTTP transport mode (`MCP_MODE=http`). The stdio transport is not affected.
### Patched
**v2.47.11** and later.
- npm: `npx n8n-mcp@latest` (or pin to `>= 2.47.11`)
- Docker: `docker pull ghcr.io/czlonkowski/n8n-mcp:latest`
### Workarounds
If users cannot upgrade immediately:
- Restrict network access to the HTTP port (firewall, reverse proxy, or VPN) so only trusted clients can reach the endpoint.
- Switch to stdio transport (`MCP_MODE=stdio`, the default for CLI invocation), which has no HTTP surface.
### Credit
n8n-MCP thanks [@S4nso](https://github.com/S4nso) (Organization / Jormungandr) for reporting this issue.
CVE-2026-41004 is a vulnerability in Spring Cloud Config Server where enabling trace logging causes sensitive information to be logged in plain text. This affects multiple versions across 3.1.x, 4.1.x, 4.2.x, 4.3.x, and 5.
HCL BigFix Service Management (SX) is affected by a Broken Access Control vulnerability leading to privilege escalation. This could allow unauthorized users to gain elevated privileges, bypassing intended access restrictions. This may result in exposure of sensitive data or unauthorized system modifications
An issue was discovered in the PaperCut Hive Ricoh embedded application. When the "Deep Logging" (diagnostic) mode is enabled, the application inadvertently records administrative credentials in plain text within the log files.
An attacker with administrative access to the PaperCut Hive management portal could remotely enable deep logging and subsequently retrieve sensitive device passwords from the logs after an authorized user authenticates at the device. This exposure allows for the lateral movement or unauthorized configuration of the physical print hardware.
CVE-2026-41182 is a vulnerability in the langchain-ai langsmith-sdk JavaScript and Python SDKs prior to versions 0.5.19 and 0.7.31 respectively. The issue arises because output redaction controls do not apply to streaming token events, allowing raw token values from streaming LLM outputs to be recorded and stored without redaction. This results in unintended exposure of sensitive information through run event data. The vulnerability has a CVSS score of 5.3, indicating medium severity. Fixed versions are available that address this issue by properly applying redaction to streaming events.
CVE-2026-40945 is a vulnerability in oxia-db's oxia metadata store and coordination system where, prior to version 0.16.2, failed OIDC authentication attempts cause the full bearer token to be logged in plaintext at DEBUG level. This exposes sensitive JWT tokens in application logs and any connected log aggregation systems if debug logging is enabled in production environments. The vulnerability has a high severity with a CVSS score of 8.7. It is fixed starting from version 0.16.2.
Dell PowerProtect Data Domain appliances running DD OS Feature Release versions 8.0 through 8.5 and LTS2025 release versions 8.3.1.0 through 8.3.1.10 have a vulnerability where sensitive information is inserted into log files. This issue affects systems with retention lock enabled and could allow a low privileged remote attacker to expose credentials.
Valtimo is an open-source business process automation platform. In versions 13.0.0 through 13.21.0, the InboxHandlingService logs the full content of every incoming inbox message at INFO level. Inbox messages can contain highly sensitive information including personal data (PII), citizen identifiers (BSN), and case details. This data is exposed to anyone with access to application logs or any Valtimo user with the admin role through the Admin UI logging module. This issue has been fixed in version 13.22.0. If developers are unable to upgrade immediately, they can restrict access to application logs and adjust the log level for com.ritense.inbox to WARN or higher in their application configuration as a workaround.
Dell PowerScale OneFS, versions prior to 9.12.0.0, contains an insertion of sensitive information into log file vulnerability. A low privileged attacker with local access could potentially exploit this vulnerability, leading to the disclosure of certain user credentials. The attacker may be able to use the exposed credentials to access the vulnerable application with privileges of the compromised account.
JWT Tokens used by tasks were exposed in logs. This could allow UI users to act as Dag Authors.
Users are advised to upgrade to Airflow version that contains fix.
Users are recommended to upgrade to version 3.2.0, which fixes this issue.
CVE-2026-40091 is a vulnerability in authzed's SpiceDB versions 1.49.0 through 1.51.0 where the startup configuration log at info level includes the full datastore DSN with the plaintext password. This sensitive information exposure occurs in the DatastoreConfig. URI field. The issue is fixed in version 1.51.1.