CVE-2026-111988
A security flaw has been discovered in dyad-sh dyad up to 1.16.0. Affected by this issue is some unknown functionality of the component OAut
CVSS
4.3
Medium
EPSS
0.2%
p9
KEV
—
Exploit Today
3
0-100
Published: Oct 18, 2026 · Last modified: Oct 19, 2026 · CWE-352 · CWE-862
Not enough EPSS history yet.
A security flaw has been discovered in dyad-sh dyad up to 1.16.0. Affected by this issue is some unknown functionality of the component OAuth Callback Handler. Performing a manipulation results in cross-site request forgery. The attack may be initiated remotely. Upgrading to version 1.17.0-beta.1 can resolve this issue. The patch is named 39fbae87b38573616a1a3b152cdb292787bb1109. It is advisable to upgrade the affected component.
- github.comhttps://github.com/dyad-sh/dyad/
- github.comhttps://github.com/dyad-sh/dyad/commit/39fbae87b38573616a1a3b152cdb292787bb1109
- github.comhttps://github.com/dyad-sh/dyad/pull/4433
- github.comhttps://github.com/dyad-sh/dyad/releases/tag/v1.17.0-beta.1
- github.comhttps://github.com/dyad-sh/dyad/security/advisories/GHSA-pqj5-w36j-2839
- vuldb.comhttps://vuldb.com/cve/CVE-2026-111988
- vuldb.comhttps://vuldb.com/submit/1007180
- vuldb.comhttps://vuldb.com/vuln/421654
- vuldb.comhttps://vuldb.com/vuln/421654/cti
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2026-86467——
——0Apache Airflow Amazon provider: the AWS auth manager's SAML login flow does not bind the authentication response to the browser that began it. The login handler discards the AuthnRequest ID and the callback validates the assertion without requiring a matching InResponseTo, so an unauthenticated attacker who can cause a victim to load a page can complete a SAML login in the victim's browser using the attacker's own assertion, silently logging the victim into the attacker's Airflow account. Subsequent work the victim performs lands in a session the attacker controls.
Affects deployments using the AWS auth manager with SAML authentication. The victim needs only to visit an attacker-controlled page; no Airflow account or credential is required of the attacker. This is the same login-CSRF class fixed in the Keycloak auth manager as CVE-2026-40948.
Users of apache-airflow-providers-amazon are recommended to upgrade to version 9.38.0, which fixes the issue.8hCVE-2026-779308.8 HIG—
——0EvoScientist 0.1.0 before 0.2.5 contains an approval bypass vulnerability that allows attackers to run host shell commands by delegating them to async sub-agents lacking an interrupt_on gate. Attackers can plant instructions in ingested content such as fetched web pages, so the agent calls start_async_task and runs commands with user privileges and environment secrets.10hCVE-2026-1094448.8 HIG—
——0OpenSRE through 0.1.2026.10.19 contains an approval gate bypass vulnerability that allows attackers to execute shell_run commands without confirmation because the headless presenter's execution_allowed() always returns True. Attackers can inject instructions into alerts or Slack messages triaged by the agent to run commands on the host and exfiltrate LLM, Slack and cloud credentials.10hCVE-2026-112778——
——0Traefik before 2.11.46, 3.x before 3.6.17, and 3.7.0 lack namespace validation for Ingress and Service annotations in the Kubernetes Ingress provider, allowing references to Middlewares, ServersTransports, and TLSOptions in other namespaces. Attackers able to create or update Ingress or Service resources in one namespace can set router.middlewares or service.serverstransport annotations to obtain another tenant's injected credentials or reuse its client certificates, bypassing namespace-based tenant isolation.13hCVE-2025-70435.4 MED—
——0The ForgeRock client fails to correctly validate refresh tokens. This allows a refresh token to be treated as a valid access token, enabling its use for consuming protected resources. This bypasses the intended security control that requires valid client credentials in addition to a refresh token to obtain a new access token.
An attacker who obtains a stolen or exposed refresh token can leverage this vulnerability to directly access protected resources. This is possible because the standard security flow requiring client credentials to exchange a refresh token for an access token is circumvented.14hCVE-2026-1110589.8 CRI—
——0Mercury is a Python framework for sharing Jupyter notebooks as web applications and dashboards. Prior to 3.2.6, default tokenless deployments allow anonymous clients to create Jupyter kernels and send execute_request messages containing arbitrary Python. The endpoint blocklist does not cover /api/kernels, and the websocket wrapper previously tracked idle activity without authorizing executable messages. This issue is fixed in version 3.2.6.14h