Monthly
IBM App Connect Enterprise 13.0.1.0 through 13.0.8.2 can expose sensitive information because components of the product may bind to an unrestricted IP address (for example 0.0.0.0 or a public interface) rather than a loopback or otherwise restricted address, leaving the listener reachable from untrusted networks. IBM's published score is 9.8 CRITICAL (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), but the assessed vector is information disclosure only (C:H/I:N/A:N): a remote, unauthenticated attacker with network reachability to the exposed listener could read data they should not have access to, without user interaction or special conditions. The practical risk is entirely governed by network exposure - deployments that firewall ACE, segment it, or bind listeners to restricted interfaces are largely shielded; no public exploit code and no CISA KEV entry were identified at time of analysis.
Unauthenticated network access to the LlamaFarm management API on port 14345 allows adjacent attackers to read stored provider API keys, modify projects, trigger data ingestion, and irreversibly delete projects in versions through 0.0.34. The insecure default binds the FastAPI server to 0.0.0.0, and the lf CLI silently ignores HOST overrides, preventing easy remediation. Exploitation requires the attacker to be on the same network segment (CVSS AV:A), and no public exploit code has been identified at time of analysis.
Unauthenticated LAN access to the ESPHome Device Builder dashboard on Home Assistant add-on deployments allows any device on the local network to gain host-equivalent control with no credentials. The ingress site, which deliberately skips authentication because the HA supervisor is supposed to authenticate upstream, was bound to 0.0.0.0 instead of loopback and the supervisor gateway. Because the add-on uses host networking for mDNS, this exposed the no-auth site on the host's LAN interface, directly bypassing the supervisor's authentication layer. An attacker with LAN access can run arbitrary Python via external_components at compile time, execute arbitrary shell through compile/validation subprocesses, and read or write arbitrary files in the config and data directories. No public exploit has been identified at time of analysis.
Remote code execution is possible in fastify-cli 1.5.0 through 8.0.0 when the Node.js Inspector is activated via a debug flag: the CLI ignores the user-supplied bind address and instead binds the Inspector to an overly broad network interface, exposing it beyond the local loopback. Because the Node.js Inspector protocol (Chrome DevTools Protocol) permits unrestricted JavaScript evaluation, any remote party that can reach the exposed Inspector port gains full code execution on the developer's machine with no authentication required. No public exploit code has been identified at time of analysis, and the EPSS signal is not provided, but the Inspector protocol itself is well-understood and trivially exploitable once the port is reachable.
Remote code execution in the Silicon One integration of Cisco Nexus 9000 Series Switches (Cisco NX-OS Software) lets an unauthenticated attacker run code as root by connecting to TCP ports 43210 and 43211, which are exposed by default in the Layer 3 default VRF. Crafted input to the S1HAL process is executed with root privileges, and the same flaw can crash S1HAL to force a device reload (denial of service). Rated CVSS 9.8; no public exploit identified at time of analysis and the CVE is not listed in CISA KEV, but the pre-authentication, network-facing nature makes it a top-priority patch.
Unauthenticated remote control of Argo CD in argocd-mcp 0.8.0, the Model Context Protocol server for Argo CD, arises because the HTTP transport binds to all network interfaces and accepts MCP sessions without any caller credential once ARGOCD_API_TOKEN is set. Any attacker with network reach to the listener can drive the full MCP tool surface under the operator's stored token to create applications, trigger syncs, and mutate Argo CD resources. Rated CVSS 10.0 by VulnCheck; no public exploit identified at time of analysis, and it is not listed in CISA KEV.
Network exposure of Docker container control ports in Spring Tools for Eclipse (versions 5.2.0 and earlier) occurs because the Boot Dashboard Docker integration binds these ports to 0.0.0.0 (all interfaces) instead of loopback. Any attacker on the same network segment as a developer running the integration can reach the container control interface without authentication, yielding high confidentiality, integrity, and availability impact. There is no public exploit identified at time of analysis and the issue is not in CISA KEV, but the flaw is trivially triggered once a developer starts the affected feature.
Remote unauthenticated manipulation of AMD Instinct GPU configuration is possible in the AMD Device Metrics Exporter (DME), a ROCm-ecosystem monitoring component, because the service binds to an unrestricted IP address and exposes its control surface network-wide. Any attacker able to reach the listening port can push unauthorized GPU configuration changes, degrading or denying availability of the affected AMD Instinct MI-series accelerator (MI210/MI250/MI250X/MI300A/MI300X/MI308X/MI325X/MI350X/MI355X). No public exploit is identified at time of analysis, and EPSS is low (0.20%), but the CVSS 4.0 base score of 9.2 reflects trivial network reachability with high availability impact.
Adjacent network code execution in gopls language server occurs when developers use debugging flags -listen or -port without explicit host specification. The Go language server (gopls) binds to all network interfaces (0.0.0.0) instead of localhost when these debugging flags are used, enabling unauthenticated remote code execution from adjacent network attackers. No public exploit identified at time of analysis, though the attack vector is straightforward for developers who enable network debugging in shared network environments like coffee shops or corporate LANs. EPSS data not available for this recent CVE.
Vulnerability in Apache IoTDB from 1.0.0 before 1.3.7 and from 2.0.0 before 2.0.7. Critical severity issue in the IoT time-series database platform.
IBM App Connect Enterprise 13.0.1.0 through 13.0.8.2 can expose sensitive information because components of the product may bind to an unrestricted IP address (for example 0.0.0.0 or a public interface) rather than a loopback or otherwise restricted address, leaving the listener reachable from untrusted networks. IBM's published score is 9.8 CRITICAL (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), but the assessed vector is information disclosure only (C:H/I:N/A:N): a remote, unauthenticated attacker with network reachability to the exposed listener could read data they should not have access to, without user interaction or special conditions. The practical risk is entirely governed by network exposure - deployments that firewall ACE, segment it, or bind listeners to restricted interfaces are largely shielded; no public exploit code and no CISA KEV entry were identified at time of analysis.
Unauthenticated network access to the LlamaFarm management API on port 14345 allows adjacent attackers to read stored provider API keys, modify projects, trigger data ingestion, and irreversibly delete projects in versions through 0.0.34. The insecure default binds the FastAPI server to 0.0.0.0, and the lf CLI silently ignores HOST overrides, preventing easy remediation. Exploitation requires the attacker to be on the same network segment (CVSS AV:A), and no public exploit code has been identified at time of analysis.
Unauthenticated LAN access to the ESPHome Device Builder dashboard on Home Assistant add-on deployments allows any device on the local network to gain host-equivalent control with no credentials. The ingress site, which deliberately skips authentication because the HA supervisor is supposed to authenticate upstream, was bound to 0.0.0.0 instead of loopback and the supervisor gateway. Because the add-on uses host networking for mDNS, this exposed the no-auth site on the host's LAN interface, directly bypassing the supervisor's authentication layer. An attacker with LAN access can run arbitrary Python via external_components at compile time, execute arbitrary shell through compile/validation subprocesses, and read or write arbitrary files in the config and data directories. No public exploit has been identified at time of analysis.
Remote code execution is possible in fastify-cli 1.5.0 through 8.0.0 when the Node.js Inspector is activated via a debug flag: the CLI ignores the user-supplied bind address and instead binds the Inspector to an overly broad network interface, exposing it beyond the local loopback. Because the Node.js Inspector protocol (Chrome DevTools Protocol) permits unrestricted JavaScript evaluation, any remote party that can reach the exposed Inspector port gains full code execution on the developer's machine with no authentication required. No public exploit code has been identified at time of analysis, and the EPSS signal is not provided, but the Inspector protocol itself is well-understood and trivially exploitable once the port is reachable.
Remote code execution in the Silicon One integration of Cisco Nexus 9000 Series Switches (Cisco NX-OS Software) lets an unauthenticated attacker run code as root by connecting to TCP ports 43210 and 43211, which are exposed by default in the Layer 3 default VRF. Crafted input to the S1HAL process is executed with root privileges, and the same flaw can crash S1HAL to force a device reload (denial of service). Rated CVSS 9.8; no public exploit identified at time of analysis and the CVE is not listed in CISA KEV, but the pre-authentication, network-facing nature makes it a top-priority patch.
Unauthenticated remote control of Argo CD in argocd-mcp 0.8.0, the Model Context Protocol server for Argo CD, arises because the HTTP transport binds to all network interfaces and accepts MCP sessions without any caller credential once ARGOCD_API_TOKEN is set. Any attacker with network reach to the listener can drive the full MCP tool surface under the operator's stored token to create applications, trigger syncs, and mutate Argo CD resources. Rated CVSS 10.0 by VulnCheck; no public exploit identified at time of analysis, and it is not listed in CISA KEV.
Network exposure of Docker container control ports in Spring Tools for Eclipse (versions 5.2.0 and earlier) occurs because the Boot Dashboard Docker integration binds these ports to 0.0.0.0 (all interfaces) instead of loopback. Any attacker on the same network segment as a developer running the integration can reach the container control interface without authentication, yielding high confidentiality, integrity, and availability impact. There is no public exploit identified at time of analysis and the issue is not in CISA KEV, but the flaw is trivially triggered once a developer starts the affected feature.
Remote unauthenticated manipulation of AMD Instinct GPU configuration is possible in the AMD Device Metrics Exporter (DME), a ROCm-ecosystem monitoring component, because the service binds to an unrestricted IP address and exposes its control surface network-wide. Any attacker able to reach the listening port can push unauthorized GPU configuration changes, degrading or denying availability of the affected AMD Instinct MI-series accelerator (MI210/MI250/MI250X/MI300A/MI300X/MI308X/MI325X/MI350X/MI355X). No public exploit is identified at time of analysis, and EPSS is low (0.20%), but the CVSS 4.0 base score of 9.2 reflects trivial network reachability with high availability impact.
Adjacent network code execution in gopls language server occurs when developers use debugging flags -listen or -port without explicit host specification. The Go language server (gopls) binds to all network interfaces (0.0.0.0) instead of localhost when these debugging flags are used, enabling unauthenticated remote code execution from adjacent network attackers. No public exploit identified at time of analysis, though the attack vector is straightforward for developers who enable network debugging in shared network environments like coffee shops or corporate LANs. EPSS data not available for this recent CVE.
Vulnerability in Apache IoTDB from 1.0.0 before 1.3.7 and from 2.0.0 before 2.0.7. Critical severity issue in the IoT time-series database platform.