The YOP Poll plugin for WordPress is vulnerable to Origin Validation Error in all versions up to, and including, 7.0.10. This is due to the plugin transmitting a wp_rest nonce to window.opener via postMessage() with a wildcard targetOrigin. This makes it possible for unauthenticated attackers to steal a REST nonce scoped to a logged-in Administrator and use it to change the Administrator's email address and password, resulting in full account takeover. The Administrator must open an attacker-controlled page in order to exploit this vulnerability.
Fabasoft Folio Client before 2026, a locally installed component that communicates with the Fabasoft browser extension via web messaging, does not restrict which web origins may invoke its functions by default. The registry value VALIDDOMAINS, which limits permitted origins, was optional and empty by default, resulting in all domains being trusted. As a consequence, any website visited by a user with the Folio Client and browser extension installed could invoke client functions, e.g., related to downloading documents, opening documents, and synchronizing files. The first fixed builds are Fabasoft Folio Client 2026 (Build 26.0.0.10) and Fabasoft Folio Client 2026 April Release (Build 26.4.0.76). This client is, for example, shipped with Fabasoft eGov-Suite.
A vulnerability in Apache Sling Security Bundle: the ReferrerFilter accepts weaker-than-orgin evidence.
This issue affects Apache Sling Security Bundle: before 1.3.2.
Users are recommended to upgrade to version 1.3.2, which fixes the issue.
CVE-2026-92701 is a critical origin validation vulnerability in Cocos AI versions 0.8.2 and earlier. The Intel TDX aTLS verifier's VerifTeeAttestation function fails to apply the expected current-session value to TdQuoteBodyPolicy.ReportData before validating TDX QuoteV4 evidence. This allows acceptance of structurally valid but mismatched or reused REPORT_DATA, potentially causing trust or authorization decisions to be made for unrelated attestation contexts. The issue was fixed in version 0.9.0 by removing the affected verifier path during migration to post-handshake attestation.
CVE-2026-92702 is a critical origin validation error in Cocos AI versions before 0.9.0. The vulnerability involves improper handling of attestation report data in the AMD SEV-SNP verifier, allowing a relying party to accept attestation evidence unrelated to the current session when empty expected report data is provided. This can lead to incorrect trust, authorization, or data release decisions. The issue was fixed in version 0.9.0 by removing the affected verification path during migration to post-handshake attestation.
Process Compose is a scheduler and orchestrator for non-containerized applications. Prior to 1.120.0, the MCP SSE listener in src/mcp/server.go accepts browser-origin requests to /sse and the returned message endpoint without validating the Host header, validating the Origin header, or authenticating the caller. When MCP SSE is enabled, a malicious website can use DNS rebinding to reach the loopback listener and issue MCP requests. If expose_control_tools is enabled, the attacker can enumerate process state, read or search logs, truncate logs, and start, stop, restart, or scale local processes; configured user-defined tools can expose additional commands and output. The Gin REST API token middleware does not protect this separately started MCP listener. This issue is fixed in version 1.120.0.
CVE-2026-89058 is a vulnerability in RESTEasy's CorsFilter that occurs when it is configured to allow all origins ('*'). The flaw causes the server to reflect the request's Origin header back in the Access-Control-Allow-Origin response and sets Access-Control-Allow-Credentials to true. This misconfiguration allows malicious websites to perform credentialed cross-origin requests and read authenticated responses from a victim's session, resulting in loss of confidentiality.
CVE-2026-77119 is a medium severity vulnerability in ISC BIND 9 involving an origin validation error. The flaw allows a validly signed NSEC3 record from an unrelated sibling zone to be incorrectly accepted as proof of insecurity. This can downgrade a secure delegation and permit acceptance of a forged unsigned DNS answer. The vulnerability affects multiple versions of BIND 9 ranging from 9.11.0 through 9.21.25, including some S1 variants.
CVE-2026-86466 is a high-severity vulnerability in the Apache Airflow FAB provider affecting versions prior to 3.9.0. The issue arises because the Authentik OAuth path in the FAB auth manager does not validate the issuer or audience claims of the id_token it accepts. This allows an attacker with a valid token for another application from the same Authentik identity provider to authenticate as any user in Airflow without proper authorization. The vulnerability is fixed in version 3.9.0.
CVE-2026-59971 is a critical vulnerability in designcomputer's mysql_mcp_server prior to version 0.4.2. The issue arises when MCP_TRANSPORT is set to sse, causing the server to construct an insecure transport without authentication or DNS rebinding protection. This allows unauthenticated network attackers to execute arbitrary SQL queries, potentially disclosing or modifying database contents. If the MySQL account has FILE privileges, attackers can read or write server files and possibly execute code. The vulnerability is fixed in version 0.4.2.
CVE-2026-57112 is a high-severity vulnerability in MervinPraison's PraisonAI multi-agent system affecting versions from 0.6.0 up to but not including 1.6.59 and 3.10.0 up to but not including 4.6.59. The issue arises because the legacy SSE wrapper mounts SseServerTransport on /sse and /messages/ endpoints without enforcing Host, Origin, or authentication checks. This allows a malicious website to perform DNS rebinding attacks to enumerate and invoke registered tools with the server user's privileges. An initial fix was released in versions 1.6.59 and 4.6.59.
dbt-mcp is a Model Context Protocol server for interacting with dbt. Prior to 1.20.0, the local OAuth helper in src/dbt_mcp/oauth/fastapi_app.py exposes GET /dbt_platform_context without authentication or Host validation after a user completes the dbt Platform OAuth flow. The endpoint returns the full DbtPlatformContext, including access_token and refresh_token values persisted by the context manager, to any process that can reach 127.0.0.1:6785. The absence of TrustedHostMiddleware allows a remote attacker to use DNS rebinding against a victim's browser because the helper accepts arbitrary Host headers, while a co-located process can request the endpoint directly. The stolen tokens provide immediate dbt Platform API access as the victim and persistent access through the refresh token, allowing access to or modification of projects, jobs, environment secrets, and related account data. This issue is fixed in version 1.20.0.
Description
Three separate mechanisms allowed a web page on an unrelated origin to read responses that Storm's HTTP
components served to an authenticated user.
The Logviewer reflected the request's `Origin` header back in `Access-Control-Allow-Origin` while also
sending `Access-Control-Allow-Credentials: true`. The published security model documents a permissive
`Access-Control-Allow-Origin: *` posture as accepted, which is safe precisely because browsers refuse to
honour `*` together with credentials; reflecting the concrete origin removes that protection.
The shared CORS filter used by the UI, the Logviewer and DRPC was configured with a response header name
where an initialisation parameter name was expected. The container ignored the setting and applied its own
defaults, which allow credentials.
Finally, the UI and Logviewer wrapped API responses in a caller-supplied JSONP callback for every GET
request. A script element on any origin can load such a response, which bypasses the same-origin policy
entirely rather than negotiating it, and there was no way to turn the behaviour off.
In each case the effect is that a page visited by an authenticated operator can read cluster, topology and
log data on their behalf.
Mitigation
Upgrade to 3.1.0, where the Logviewer no longer reflects the request origin in a credentialed response, the
CORS filter is configured explicitly, and JSONP wrapping is governed by `ui.enable.jsonp`, which defaults to
false.
Note that disabling JSONP is a behaviour change for tooling that passes a `callback` query parameter; such
tooling should be moved to ordinary JSON requests.
Users who cannot upgrade immediately should place the UI, Logviewer and DRPC HTTP endpoints behind a reverse
proxy that strips `Access-Control-Allow-Origin` and `Access-Control-Allow-Credentials` from responses and
rejects requests carrying a `callback` parameter.
Credit
The ASF -- found using Claude agents to study the security of open-source projects, validated and reported by Apache Storm.
An issue was discovered in NR RRC in Samsung Mobile Processor and Modem Exynos 1080, 2100, 1280, 2200, 1330, 1380, 1480, 2400, 1580, 2500, W1000, Modem 5300, Modem 5400, and Modem 5410. Incorrect handling of unauthenticated downlink RRC Setup messages can cause the baseband to crash.
Mousehole is a background service to update a seedbox IP for MAM and web app to manage it. Prior to version 0.4.05, Mousehole's HTTP/WebSocket management boundary is reachable without application-layer authentication or browser/LAN provenance checks. The service stores a MyAnonamouse (MAM) session cookie in state and reuses the same cookie-bearing serialization for persisted state, public API responses, and WebSocket state updates. Any client that can reach the published Mousehole port can read cookie-bearing state, connect to WebSocket state updates, replace the stored cookie, or force MAM update side effects. The deployment examples publish port 5010 broadly with Docker's `5010:5010` syntax, which can make the issue reachable on mixed-trust LAN/VPN interfaces. Version 0.4.0 patches the issue.
CVE-2026-58649 is an origin validation error vulnerability in the Microsoft .NET 10.0 runtime that allows an unauthorized attacker to disclose information over a network. The flaw affects multiple versions of the .NET runtime, including 8.0.0, 9.0.0, 10.0.0, 11.0.0, and certain 17.x and 18.x releases prior to fixed versions. The vulnerability has a medium severity rating with a CVSS score of 6.5. An official fix is available from Microsoft.
CVE-2026-69559 is an origin validation error vulnerability in Microsoft Teams for Android that allows an authorized attacker to disclose information over a network. The vulnerability affects versions from 1.0.0 up to but not including 1.0.0.2026142702. A fix is available in version 1.0.0.2026142702. The vulnerability has a medium severity with a CVSS score of 5.8.
CVE-2026-69680 is an origin validation error vulnerability in the Windows DNS component affecting multiple versions of Microsoft Windows, including Windows 10 Version 1607. This flaw allows an unauthorized attacker to perform network spoofing attacks. The vulnerability has a high severity score of 8.1 and has been officially fixed by Microsoft in specific updates.
Apache Airflow FAB provider versions 3.7.3 through 3.8.0 do not validate the issuer or audience of Azure AD `id_token`s during OAuth login. Deployments are affected only when the FAB auth manager is configured with Azure AD as an OAuth provider. Because the signing keys are fetched from Microsoft's **multi-tenant** JWKS endpoint, an `id_token` minted in *any* Azure tenant — including one the attacker creates — passes signature verification, and the username and role assignments are then read from that attacker-controlled token. Anyone able to register an Azure tenant can therefore authenticate to the Airflow UI with no prior access to the deployment.
The fix for **CVE-2026-59243** was incomplete, and this advisory closes the remaining gap: that fix made the provider verify the `id_token` signature, but did not add issuer or audience checks. Operators who already applied the CVE-2026-59243 fix are **still affected and must upgrade again** — 3.7.3 is the release that shipped that fix, so every version containing it falls inside this affected range. Upgrade to apache-airflow-providers-fab `3.8.1` or later.