Monthly
Port forwarding in GitHub CLI versions 2.28.0 through 2.97.0 binds its local TCP listener to all network interfaces (0.0.0.0) rather than loopback only, exposing forwarded Codespace services to any adjacent host that can route to the user's machine while `gh codespace ports forward` is active. Developers using this command on shared or untrusted networks - corporate Wi-Fi, conference networks, co-working LAN segments - may unintentionally expose Codespace services that were intended to remain private. The vulnerability is fixed in v2.98.0 per advisory GHSA-vfhh-p7hm-pxfh; no public exploit code and no CISA KEV listing have been identified at time of analysis.
Improper resource exposure in Google Chrome's StreamsAPI (versions prior to 152.0.7977.65) enables remote attackers to partially bypass the web origin policy and read limited data from privileged browser pages via a crafted HTML page. Exploitation requires user interaction - the victim must visit an attacker-controlled page - consistent with CVSS UI:R and S:U, confining impact to the victim's own browser context. No active exploitation is confirmed (not in CISA KEV), and an EPSS score of 0.18% (8th percentile) indicates very low real-world exploitation probability at time of analysis.
Improper resource exposure in Google Chrome's Preload mechanism prior to version 152.0.7977.65 enables remote attackers to bypass Site Isolation by luring a user to a crafted HTML page. The flaw (CWE-668) allows cross-origin resource data to leak across security boundaries, undermining Chrome's core renderer isolation architecture and potentially exposing sensitive information from other origins loaded in the browser. No public exploit has been identified at time of analysis; EPSS at 0.39% (32nd percentile) and the absence of a CISA KEV listing indicate low but non-zero exploitation probability.
Spring AI 2.0.0's Semantic Cache feature leaks cached LLM responses across unrelated system prompt contexts due to insufficient isolation in the context hashing mechanism. Applications using semantic caching across multiple tenants or security domains - where different system prompts define distinct access boundaries - are at risk of cross-context information disclosure and response tampering. Exploitation requires authenticated access and high attack complexity (AC:H, PR:L); no public exploit code and no CISA KEV listing exist at time of analysis.
Craft CMS exposes arbitrary environment variables and secrets to authenticated control panel users due to premature interpolation of ${ENV_VAR} patterns in the elementId parameter before Twig sandbox evaluation - a design flaw that bypasses the sandbox entirely because substitution occurs outside the renderer. Affected versions span both the 4.x and 5.x release lines from their respective RC1 milestones through just before 4.18.2 and 5.10.6. An attacker holding any control panel account can exfiltrate CRAFT_SECURITY_KEY and all other configured secrets via a blind, error-based extraction loop, enabling session forgery, privilege escalation, and theft of database, SMTP, API, and blob storage credentials; no public exploit or active exploitation has been identified at time of analysis.
Cross-user module cache poisoning in n8n's JavaScript task runner allows an authenticated Code-node user to inject malicious logic into a shared module cache, silently altering other users' workflow executions on the same instance and compromising their data confidentiality, workflow integrity, or execution availability. Affects all multi-user n8n deployments on versions before 1.123.67 (1.x), 2.31.5 (2.31.x), and 2.32.1 (2.32.x) where the JS task runner is active and built-in or external module access is enabled. No public exploit has been identified at time of analysis, and the vulnerability is not listed in CISA KEV; despite the 'RCE' tag applied by the reporting source, the vendor advisory explicitly confirms this is a cross-user isolation break and not a sandbox escape or remote code execution.
Session isolation bypass in Electron's custom protocol handler allows cached HTTP responses from defaultSession to leak across otherwise isolated session partitions. Electron versions 40.x through pre-release 43.x are affected when apps use ProtocolResponse.url without specifying ProtocolResponse.session, causing upstream requests to be routed through defaultSession regardless of which session registered the protocol handler. An attacker who can trigger a cross-session cache hit may read confidential session-scoped content (C:H) or partially influence cached responses (I:L) intended for a different, isolated session; no public exploit or CISA KEV listing exists at time of analysis.
Cross-container isolation bypass in proot-distro 5.1.5 and earlier (Termux) lets a crafted backup archive read and write files across otherwise isolated containers when a victim runs 'proot-distro restore'. Because the restore logic trusts the archive's hardlink 'linkname' to name the source container without verifying it matches the container being restored, an attacker who convinces a user to restore a malicious .tar can exfiltrate secrets (SSH keys, API credentials, databases) from one container into an attacker-controlled one, or inject attacker data into a different container. Publicly available exploit code exists (full PoCs are embedded in the GHSA advisory); no public active exploitation is known.
Cross-namespace information disclosure in open-feature-operator allows a tenant with workload creation privileges to read another tenant's FeatureFlagSource or InProcessConfiguration spec contents on multi-tenant Kubernetes clusters. The operator resolves references across namespace boundaries using a documented annotation syntax, leaking inline env vars, bearer tokens, and sync URIs into the attacker's pod. No public exploit has been identified, and the behavior is intentional but contradicts namespace-as-trust-boundary expectations.
Exposure of a scanning VM's VNC service in Fortinet FortiSandbox 5.0.0-5.0.2 and 4.4.3-4.4.8 lets an unauthenticated remote attacker reach the VNC server of the sandbox virtual machines used for malware detonation via ordinary network requests. Because these VMs run and observe live malware samples, unauthorized VNC access can expose sensitive analysis sessions and potentially allow interaction with the detonation environment. No public exploit identified at time of analysis, and the issue is not listed in CISA KEV.
Port forwarding in GitHub CLI versions 2.28.0 through 2.97.0 binds its local TCP listener to all network interfaces (0.0.0.0) rather than loopback only, exposing forwarded Codespace services to any adjacent host that can route to the user's machine while `gh codespace ports forward` is active. Developers using this command on shared or untrusted networks - corporate Wi-Fi, conference networks, co-working LAN segments - may unintentionally expose Codespace services that were intended to remain private. The vulnerability is fixed in v2.98.0 per advisory GHSA-vfhh-p7hm-pxfh; no public exploit code and no CISA KEV listing have been identified at time of analysis.
Improper resource exposure in Google Chrome's StreamsAPI (versions prior to 152.0.7977.65) enables remote attackers to partially bypass the web origin policy and read limited data from privileged browser pages via a crafted HTML page. Exploitation requires user interaction - the victim must visit an attacker-controlled page - consistent with CVSS UI:R and S:U, confining impact to the victim's own browser context. No active exploitation is confirmed (not in CISA KEV), and an EPSS score of 0.18% (8th percentile) indicates very low real-world exploitation probability at time of analysis.
Improper resource exposure in Google Chrome's Preload mechanism prior to version 152.0.7977.65 enables remote attackers to bypass Site Isolation by luring a user to a crafted HTML page. The flaw (CWE-668) allows cross-origin resource data to leak across security boundaries, undermining Chrome's core renderer isolation architecture and potentially exposing sensitive information from other origins loaded in the browser. No public exploit has been identified at time of analysis; EPSS at 0.39% (32nd percentile) and the absence of a CISA KEV listing indicate low but non-zero exploitation probability.
Spring AI 2.0.0's Semantic Cache feature leaks cached LLM responses across unrelated system prompt contexts due to insufficient isolation in the context hashing mechanism. Applications using semantic caching across multiple tenants or security domains - where different system prompts define distinct access boundaries - are at risk of cross-context information disclosure and response tampering. Exploitation requires authenticated access and high attack complexity (AC:H, PR:L); no public exploit code and no CISA KEV listing exist at time of analysis.
Craft CMS exposes arbitrary environment variables and secrets to authenticated control panel users due to premature interpolation of ${ENV_VAR} patterns in the elementId parameter before Twig sandbox evaluation - a design flaw that bypasses the sandbox entirely because substitution occurs outside the renderer. Affected versions span both the 4.x and 5.x release lines from their respective RC1 milestones through just before 4.18.2 and 5.10.6. An attacker holding any control panel account can exfiltrate CRAFT_SECURITY_KEY and all other configured secrets via a blind, error-based extraction loop, enabling session forgery, privilege escalation, and theft of database, SMTP, API, and blob storage credentials; no public exploit or active exploitation has been identified at time of analysis.
Cross-user module cache poisoning in n8n's JavaScript task runner allows an authenticated Code-node user to inject malicious logic into a shared module cache, silently altering other users' workflow executions on the same instance and compromising their data confidentiality, workflow integrity, or execution availability. Affects all multi-user n8n deployments on versions before 1.123.67 (1.x), 2.31.5 (2.31.x), and 2.32.1 (2.32.x) where the JS task runner is active and built-in or external module access is enabled. No public exploit has been identified at time of analysis, and the vulnerability is not listed in CISA KEV; despite the 'RCE' tag applied by the reporting source, the vendor advisory explicitly confirms this is a cross-user isolation break and not a sandbox escape or remote code execution.
Session isolation bypass in Electron's custom protocol handler allows cached HTTP responses from defaultSession to leak across otherwise isolated session partitions. Electron versions 40.x through pre-release 43.x are affected when apps use ProtocolResponse.url without specifying ProtocolResponse.session, causing upstream requests to be routed through defaultSession regardless of which session registered the protocol handler. An attacker who can trigger a cross-session cache hit may read confidential session-scoped content (C:H) or partially influence cached responses (I:L) intended for a different, isolated session; no public exploit or CISA KEV listing exists at time of analysis.
Cross-container isolation bypass in proot-distro 5.1.5 and earlier (Termux) lets a crafted backup archive read and write files across otherwise isolated containers when a victim runs 'proot-distro restore'. Because the restore logic trusts the archive's hardlink 'linkname' to name the source container without verifying it matches the container being restored, an attacker who convinces a user to restore a malicious .tar can exfiltrate secrets (SSH keys, API credentials, databases) from one container into an attacker-controlled one, or inject attacker data into a different container. Publicly available exploit code exists (full PoCs are embedded in the GHSA advisory); no public active exploitation is known.
Cross-namespace information disclosure in open-feature-operator allows a tenant with workload creation privileges to read another tenant's FeatureFlagSource or InProcessConfiguration spec contents on multi-tenant Kubernetes clusters. The operator resolves references across namespace boundaries using a documented annotation syntax, leaking inline env vars, bearer tokens, and sync URIs into the attacker's pod. No public exploit has been identified, and the behavior is intentional but contradicts namespace-as-trust-boundary expectations.
Exposure of a scanning VM's VNC service in Fortinet FortiSandbox 5.0.0-5.0.2 and 4.4.3-4.4.8 lets an unauthenticated remote attacker reach the VNC server of the sandbox virtual machines used for malware detonation via ordinary network requests. Because these VMs run and observe live malware samples, unauthorized VNC access can expose sensitive analysis sessions and potentially allow interaction with the detonation environment. No public exploit identified at time of analysis, and the issue is not listed in CISA KEV.