Monthly
Cross-session credential isolation failure in rclone's FTP auth-proxy driver (versions 1.64.0-1.75.0) allows an authenticated network attacker to hijack a victim user's cloud storage backend by exploiting a server-wide, username-keyed credential map. When an attacker holds an open FTP session using a shared username and a victim subsequently authenticates with the same username, the victim's credential silently overwrites the server-wide map entry - causing the attacker's subsequent VFS operations to execute against the victim's backend, enabling reads, writes, renames, and deletions of the victim's cloud objects. No public exploit identified at time of analysis; vendor-released patch v1.75.1 resolves the issue.
Cross-tenant GitHub App installation token theft in JetBrains YouTrack before 2026.2.18634 lets any authenticated user retrieve GitHub App installation tokens belonging to other tenants due to a shared, non-isolated token cache. The root cause is CWE-488 (Exposure of Data Element to Wrong Session): cached tokens were keyed without tenant-scope isolation. With a stolen installation token, an attacker can authenticate to the GitHub API as the victim organization's GitHub App, gaining access to that organization's repositories, pull requests, issues, and CI/CD integrations; no public exploit has been identified at time of analysis.
Session isolation failure in IBM ContextForge MCP Gateway - Translate Utility (≤ 1.0.8) permits unauthenticated remote attackers to access session data belonging to other users and potentially inject content into those sessions, due to improper enforcement of session boundaries (CWE-488). The CVSS AC:H metric indicates exploitation depends on specific timing or concurrency conditions - likely a race condition or shared mutable state in multi-tenant request handling - rather than a trivially triggerable flaw. IBM has released a remediation; no public exploit code has been identified at time of analysis.
Cross-user session confusion in libcurl allows one user's HTTP request to be silently transmitted over another user's previously authenticated Negotiate (SPNEGO/Kerberos) connection. When an initial request to a host is made with empty credentials, libcurl incorrectly treats the resulting connection as eligible for reuse, so a subsequent request from a different principal inherits the earlier authenticated context. There is no public exploit identified at time of analysis; EPSS is low (0.26%, 17th percentile), and the flaw is only meaningful in multi-user or proxy-style deployments that share a single libcurl handle/connection pool.
Connection pool mismanagement in libcurl silently reuses HTTPS connections across requests that differ in their `CURLSSLOPT_NATIVE_CA` (Native CA Store) SSL option, affecting all curl releases from 7.71.0 through 8.21.0. When an application uses a shared connection pool to the same hostname with mixed native CA settings, libcurl fails to distinguish connections by their CA trust configuration, potentially applying the wrong certificate authority validation to a subsequent request. No public exploit code exists and EPSS sits at 0.21% (12th percentile), indicating low active exploitation probability, though the vulnerability's broad version footprint - spanning several years of releases - makes it relevant wherever libcurl is deployed with mixed native CA configurations.
Cross-session token leakage in HashiCorp consul-mcp-server 0.1.0 through 0.1.3 allows one client's Consul authentication token to bleed into requests issued by other clients when the server runs in stateless mode, effectively enabling an attacker to act against Consul with a victim's credentials. HashiCorp rated this CVSS 10.0 (scope-changed) because the borrowed token grants the attacker the victim's full Consul read/write authority across a trust boundary. There is no public exploit identified at time of analysis, and it is not listed in CISA KEV; the fix is consul-mcp-server 0.1.4.
Credential reuse in Terraform MCP Server allows cross-tenant token leakage, enabling unauthorized tool execution on behalf of other users. The vulnerability affects versions prior to 1.1.0 when the server is run in streamable-HTTP stateless transport mode. No public exploit code is known, but the critical CVSS score and network attack vector indicate high potential risk.
Zabbix Server and Proxy reuse JavaScript (Duktape) execution contexts across script items, JavaScript preprocessing, and webhooks for performance optimization, allowing non-super administrators to leak sensitive data about hosts they lack authorization to access through context variable persistence. The vulnerability enables information disclosure attacks where a regular administrator can access confidential monitoring data from restricted hosts by exploiting shared JavaScript execution environments. A patch has been released that makes built-in Zabbix JavaScript objects read-only, though global variable usage remains unsafe even after remediation.
Pulp Ansible's bearer-token refresh for collection remotes can disclose access tokens to an authenticated attacker who can create or sync a remote and point it at a malicious server. The attacker must then reuse the token at the issuing service, and exploitation is only possible if another token download for a different remote has run on the same worker process, meaning shared, multi-tenant deployments are primarily at risk. No public exploit code exists, and the assessed attack complexity is high (AC:H), so this is a moderate-priority information disclosure issue rather than a top-tier emergency.
Authenticated users with permission to create and sync container remotes in Pulp can obtain upstream registry credentials-usernames, passwords, or bearer tokens-stored for other remotes because the pulp-container worker reuses authentication material across sync operations. This affects deployments built on Red Hat Ansible Automation Platform 2, Red Hat Satellite 6, and Red Hat Update Infrastructure 4/5, particularly multi-tenant environments where remotes share worker processes. No public exploit code or confirmed active exploitation has been identified; the flaw rates CVSS 6.5 (moderate) and requires no user interaction beyond the attacker's own sync, though it does require an authenticated user with remote-creation and sync privileges.
Cross-session credential isolation failure in rclone's FTP auth-proxy driver (versions 1.64.0-1.75.0) allows an authenticated network attacker to hijack a victim user's cloud storage backend by exploiting a server-wide, username-keyed credential map. When an attacker holds an open FTP session using a shared username and a victim subsequently authenticates with the same username, the victim's credential silently overwrites the server-wide map entry - causing the attacker's subsequent VFS operations to execute against the victim's backend, enabling reads, writes, renames, and deletions of the victim's cloud objects. No public exploit identified at time of analysis; vendor-released patch v1.75.1 resolves the issue.
Cross-tenant GitHub App installation token theft in JetBrains YouTrack before 2026.2.18634 lets any authenticated user retrieve GitHub App installation tokens belonging to other tenants due to a shared, non-isolated token cache. The root cause is CWE-488 (Exposure of Data Element to Wrong Session): cached tokens were keyed without tenant-scope isolation. With a stolen installation token, an attacker can authenticate to the GitHub API as the victim organization's GitHub App, gaining access to that organization's repositories, pull requests, issues, and CI/CD integrations; no public exploit has been identified at time of analysis.
Session isolation failure in IBM ContextForge MCP Gateway - Translate Utility (≤ 1.0.8) permits unauthenticated remote attackers to access session data belonging to other users and potentially inject content into those sessions, due to improper enforcement of session boundaries (CWE-488). The CVSS AC:H metric indicates exploitation depends on specific timing or concurrency conditions - likely a race condition or shared mutable state in multi-tenant request handling - rather than a trivially triggerable flaw. IBM has released a remediation; no public exploit code has been identified at time of analysis.
Cross-user session confusion in libcurl allows one user's HTTP request to be silently transmitted over another user's previously authenticated Negotiate (SPNEGO/Kerberos) connection. When an initial request to a host is made with empty credentials, libcurl incorrectly treats the resulting connection as eligible for reuse, so a subsequent request from a different principal inherits the earlier authenticated context. There is no public exploit identified at time of analysis; EPSS is low (0.26%, 17th percentile), and the flaw is only meaningful in multi-user or proxy-style deployments that share a single libcurl handle/connection pool.
Connection pool mismanagement in libcurl silently reuses HTTPS connections across requests that differ in their `CURLSSLOPT_NATIVE_CA` (Native CA Store) SSL option, affecting all curl releases from 7.71.0 through 8.21.0. When an application uses a shared connection pool to the same hostname with mixed native CA settings, libcurl fails to distinguish connections by their CA trust configuration, potentially applying the wrong certificate authority validation to a subsequent request. No public exploit code exists and EPSS sits at 0.21% (12th percentile), indicating low active exploitation probability, though the vulnerability's broad version footprint - spanning several years of releases - makes it relevant wherever libcurl is deployed with mixed native CA configurations.
Cross-session token leakage in HashiCorp consul-mcp-server 0.1.0 through 0.1.3 allows one client's Consul authentication token to bleed into requests issued by other clients when the server runs in stateless mode, effectively enabling an attacker to act against Consul with a victim's credentials. HashiCorp rated this CVSS 10.0 (scope-changed) because the borrowed token grants the attacker the victim's full Consul read/write authority across a trust boundary. There is no public exploit identified at time of analysis, and it is not listed in CISA KEV; the fix is consul-mcp-server 0.1.4.
Credential reuse in Terraform MCP Server allows cross-tenant token leakage, enabling unauthorized tool execution on behalf of other users. The vulnerability affects versions prior to 1.1.0 when the server is run in streamable-HTTP stateless transport mode. No public exploit code is known, but the critical CVSS score and network attack vector indicate high potential risk.
Zabbix Server and Proxy reuse JavaScript (Duktape) execution contexts across script items, JavaScript preprocessing, and webhooks for performance optimization, allowing non-super administrators to leak sensitive data about hosts they lack authorization to access through context variable persistence. The vulnerability enables information disclosure attacks where a regular administrator can access confidential monitoring data from restricted hosts by exploiting shared JavaScript execution environments. A patch has been released that makes built-in Zabbix JavaScript objects read-only, though global variable usage remains unsafe even after remediation.
Pulp Ansible's bearer-token refresh for collection remotes can disclose access tokens to an authenticated attacker who can create or sync a remote and point it at a malicious server. The attacker must then reuse the token at the issuing service, and exploitation is only possible if another token download for a different remote has run on the same worker process, meaning shared, multi-tenant deployments are primarily at risk. No public exploit code exists, and the assessed attack complexity is high (AC:H), so this is a moderate-priority information disclosure issue rather than a top-tier emergency.
Authenticated users with permission to create and sync container remotes in Pulp can obtain upstream registry credentials-usernames, passwords, or bearer tokens-stored for other remotes because the pulp-container worker reuses authentication material across sync operations. This affects deployments built on Red Hat Ansible Automation Platform 2, Red Hat Satellite 6, and Red Hat Update Infrastructure 4/5, particularly multi-tenant environments where remotes share worker processes. No public exploit code or confirmed active exploitation has been identified; the flaw rates CVSS 6.5 (moderate) and requires no user interaction beyond the attacker's own sync, though it does require an authenticated user with remote-creation and sync privileges.