CVE-2026-11624
CriticalCVSS 9.4Exploitation Probability (EPSS)
Low risk5th percentile - higher than 5% of all known CVEs
Summary
Model Context Protocol (MCP) before version 0.25.0 lacked Origin header validation to prevent DNS rebinding attacks. Version 0.25.0 introduces the --allowed-hosts flag, which defaults to '*' and warns about potential vulnerabilities.
Risk Assessment
Risk of DNS rebinding attacks that could allow an attacker to hijack sessions or access protected MCP server resources.
Recommendation
Upgrade Model Context Protocol to version 0.25.0 or later and configure the --allowed-hosts and --allowed-origins flags according to security requirements.
Related vulnerabilities
- CVE-2026-102428Critical
The Joomla extension OrdaSoft CCK before version 8.3.16 contains an unauthenticated SQL injection vulnerability. The order column for records was user provided and not properly validated, leading to a SQL injection vector.
- CVE-2026-79820Critical
A remote user validation failure vulnerability exists in HPE Integrated Lights-Out (iLO) 7 firmware.
- CVE-2026-105285Critical
A vulnerability has been detected in Totolink A3002MU version 1.0.0-B20230403.1455. It affects an unknown function in the file /boafrm/formIpQoS of the QoS Rule Handler component. Manipulation of the addQos/comment/entry_name arguments leads to a stack-based buffer overflow. The attack can be performed remotely, and the exploit has been publicly disclosed.
- CVE-2026-105284Critical
A weakness has been identified in Totolink A3002MU version 1.0.0-B20230403.1455. It affects the function sub_40FCFC in the file /bin/boa of the Authentication Check component. Executing a manipulation can lead to improper authorization. The attack can be launched remotely, and the exploit has been made publicly available.
- CVE-2026-103510Critical
P4 Search prior to 2026.4.2 does not fail securely when its service authentication token is blank. In affected configurations, an unauthenticated attacker with network access can obtain the highest application privilege, potentially leading to compromise of P4 Search and the connected P4 Server.
- CVE-2026-100103Critical
Perforce P4 Search container images prior to 2026.4.2 reset the service authentication token to a publicly documented default value. An unauthenticated attacker with network access can obtain the highest application privilege, potentially leading to arbitrary code execution and compromise of the connected P4 Server.
- CVE-2026-100102Critical
Perforce P4 Search container images prior to 2026.4.2 enable an unauthenticated Java debug interface. An attacker with network access to this interface can execute arbitrary code as the P4 Search service account, potentially leading to compromise of the connected P4 Server.
- CVE-2026-105215Critical
ZITADEL before 3.4.14 and 4.x before 4.16.2 contains an authentication bypass in the hosted Login V1 UI because the 'external account not found' registration endpoint trusts client-supplied external identity fields without a completed IdP callback. Unauthenticated attackers can submit forged IDPConfigID and ExternalUserID values to pre-create an account bound to a victim's external IdP identity, which the victim's later genuine external login then signs into.
- CVE-2026-105209Critical
ZITADEL 3.x before 3.4.15 and 4.x before 4.17.1 contains an improper authorization vulnerability: when issuing passkey or passwordless enrollment codes, it checks only the organization in the x-zitadel-orgid header, not the target user's organization. Attackers with user-write permission in one organization can obtain an enrollment code for a user in another organization on the same instance and register their own authenticator to take over that account.
- CVE-2026-105207Critical
ZITADEL 3.0.0 through 3.4.15 and 4.0.0 before 4.17.3 creates links between user accounts and external identity providers without verifying a primary factor or the caller's permission, including on identify-only Login V2 sessions and via the User Service V2 AddIDPLink endpoint. An unauthenticated attacker knowing a victim's login name can bind their own external IdP identity to the victim's account and then sign in as the victim.
Original NVD description (English source)
The Model Context Protocol has a security warning advising servers to validate the "Origin" header on all incoming connections to prevent DNS rebinding attacks. Prior to the v0.25.0 release, users had no way to validate the origin's host. In v0.25.0, a new "--allowed-hosts" flag was introduced alongside the existing "--allowed-origins" flag, enabling users to specify permitted hosts at server startup. Both flags default to "*", allowing users to implement strict access controls as needed without breaking existing setups. If either flag is set to "*", the server will output a startup warning about potential vulnerabilities. Documentation has also been updated to highlight these security considerations.
Vulnerability data from NVD (NIST) · CISA KEV · EPSS

