draw.io is a configurable diagramming and whiteboarding application. Prior to version 29.7.9, the draw.io client accepts a ?gitlab= URL parameter that overrides the GitLab server URL used during OAuth sign-in. A crafted link causes the user's click on draw.io's "Authorize in GitLab" dialog to open a popup on the attacker-controlled host instead of gitlab.com. This can lead to credential fishing and session state token exfiltration. This issue has been patched in version 29.7.9.
Open redirection vulnerability in the latest demo version of the Cradle eCommerce platform. The vulnerability occurs in the login form endpoint, where the ‘returnUrl’ parameter allows redirection because the web application accepts a URL as a parameter without properly validating it. As a result, it is possible to redirect users from the legitimate website to external pages. An attacker could exploit this vulnerability to deceive users and redirect them from a trusted URL to a malicious one without their knowledge.
Electerm versions 3.8.15 and earlier contain a critical vulnerability where the terminal hyperlink handler passes clicked URLs directly to shell.openExternal without validating the protocol. This allows an attacker who controls terminal output to execute arbitrary code or access local files if the victim clicks a malicious link. No patches are publicly available at the time of disclosure.
CVE-2026-42259 is an open redirect vulnerability in Saltcorn, an open source no-code database application builder. Versions prior to 1.4.6, 1.5.6, and 1.6.0-beta.5 improperly validate the post-login destination URL, allowing specially crafted URLs with backslashes to bypass checks and redirect users to attacker-controlled domains. This vulnerability can be triggered by tricking a user into logging in via a malicious URL. The issue has been fixed in the specified patched versions.
URL redirection to untrusted site ('open redirect') vulnerability in DivvyDrive Information Technologies Inc. DivvyDrive allows Parameter Injection.
This issue affects DivvyDrive: from 4.8.2.9 before 4.8.3.2.
Admidio versions prior to 5.0.9 contain an improper input validation vulnerability in the SAML IdP implementation of its SSO module. The system uses the AssertionConsumerServiceURL from incoming SAML AuthnRequest messages without verifying it against the registered URL for the service provider. This allows an attacker who knows a registered service provider's Entity ID to craft a request that causes the IdP to send signed SAML responses containing user identity attributes to an attacker-controlled URL. This vulnerability is fixed in version 5.0.9.
Masa CMS has an Open Redirect vulnerability caused by improper handling of scheme-relative URLs starting with double slashes (//). The application treats these as internal paths without validating that the redirect target remains local, allowing attackers to redirect users to external malicious sites. This can facilitate phishing attacks and potentially expose sensitive tokens in some authentication flows. The issue is fixed in versions 7.2.10, 7.3.15, 7.4.10, and 7.5.3. Workarounds include rejecting or rewriting redirect parameters that begin with // and disabling forceDirectoryStructure if compatible.
OpenClaw before version 2026.4.5 contains a server-side request forgery (SSRF) vulnerability in the CDP /json/version WebSocket endpoint. The vulnerability arises because the webSocketDebuggerUrl response field is not properly validated, allowing attackers to redirect connections to arbitrary hosts. This enables SSRF-style attacks by pivoting to untrusted second-hop targets.
The backend for Jupyter web applications
Security Fix(es):
Jupyter Server is the backend for Jupyter web applications. In jupyter_server versions through 2.17.0, the next query parameter in the login flow is insufficiently validated in `LoginFormHandler._redirect_safe()`, which allows redirects to arbitrary external domains via values such as `///example.com`. An attacker can use a crafted login URL to redirect users to a malicious site and facilitate phishing attacks. This issue is fixed in version 2.18.0.(CVE-2025-61669)
Jupyter Server is the backend for Jupyter web applications. In versions 2.17.0 and earlier, a path traversal vulnerability in the REST API allows an authenticated user to escape the configured root_dir and access sibling directories whose names begin with the same prefix as the root_dir. For example, with a root_dir named "test", the API permits access to a sibling directory named "testtest" through a crafted request to the /api/contents endpoint using encoded path components. An attacker can read, write, and delete files in affected sibling directories. Multi-tenant deployments using predictable naming schemes are particularly at risk, as a user with a directory named "user1" could access directories for user10 through user19 and beyond. A user who can choose a single-character folder name could gain access to a significant number of sibling directories.
Version 2.18.0 contains a fix. As a workaround, ensure folder names do not share a common prefix with any sibling directory.(CVE-2026-35397)
Jupyter Server is the backend for Jupyter web applications. In versions 2.17.0 and earlier, the Origin header validation uses Python's re.match() to check incoming origins against the allow_origin_pat configuration value. Because re.match() only anchors at the start of the string and does not require a full match, a pattern intended to match only a trusted domain (e.g., trusted.example.com) will also match any origin that begins with that domain followed by additional characters (e.g., trusted.example.com.evil.com). An attacker who controls such a domain can bypass the CORS origin restriction and make cross-origin requests to the Jupyter Server API from an untrusted site. This issue has been fixed in version 2.18.0.(CVE-2026-40110)
Jupyter Server is the backend for Jupyter web applications. In versions 2.17.0 and earlier, the secret used to sign authentication cookies is persisted to a static file at ~/.local/share/jupyter/runtime/jupyter_cookie_secret and is never rotated when a user changes their password. After a password reset and server restart, any previously issued authentication cookie remains cryptographically valid because the signing key has not changed. An attacker who has captured a session cookie through any means retains full authenticated access to the server regardless of subsequent password changes. This affects deployments using password-based authentication, particularly shared or public-facing servers where credential rotation is expected to revoke existing sessions. This issue has been fixed in version 2.18.0.(CVE-2026-40934)
n8n is an open source workflow automation platform. Prior to versions 1.123.32, 2.17.4, and 2.18.1, the /mcp-oauth/register endpoint accepted OAuth client registrations without authentication, allowing arbitrary redirect_uri values to be registered. When a user denies the MCP OAuth consent dialog, the handleDeny handler redirects the user to the registered redirect_uri without validation, enabling an open redirect to an attacker-controlled URL. An attacker can craft a phishing link and send it to a victim; if the victim clicks "Deny" on the consent page, they are silently redirected to an external site. This issue has been patched in versions 1.123.32, 2.17.4, and 2.18.1.
Open redirect vulnerability exists in Multiple laser printers and MFPs which implement Ricoh Web Image Monitor. When accessing a specially crafted URL, the user may be redirected to an arbitrary website. As a result, the user may become a victim of a phishing attack.
LinkAce is a self-hosted archive to collect website links. Prior to 2.5.4, a password reset poisoning vulnerability was identified in the application due to improper trust of user-controlled HTTP headers. The application uses the X-Forwarded-Host header when generating password reset URLs. By manipulating this header during a password reset request, an attacker can inject an attacker-controlled domain into the reset link sent via email. As a result, the victim receives a password reset email containing a malicious link pointing to an attacker-controlled domain. When the victim clicks the link, the password reset token is transmitted to the attacker-controlled server. An attacker can capture this token and use it to reset the victim’s password, leading to full account takeover. This vulnerability is fixed in 2.5.4.
next-intl provides internationalization for Next.js. Applications using the `next-intl` middleware prior to version 4.9.1with `localePrefix: 'as-needed'` could construct URLs where path handling and the WHATWG URL parser resolved a relative redirect target to another host (e.g.scheme-relative `//` or control characters stripped by the URL parser), so the middleware could redirect the browser off-site while the user still started from a trusted app URL. The problem has been patchedin `next-intl@4.9.1`.
A vulnerability in AdonisJS HTTP Server prior to versions 7.8.1 and 8.2.0 allows an attacker to exploit the response.redirect(). back() method. This method improperly trusts the Referer header from incoming requests and redirects users to that URL without validating the host. An attacker who can control the Referer header can redirect users to malicious external sites. This open redirect issue affects all AdonisJS applications using this method in the specified vulnerable versions.
immich versions prior to 2.7.3 contain a cross-site scripting (XSS) vulnerability due to improper input neutralization in the shared album feature. An attacker can craft an album name that injects a malicious meta refresh tag, causing victim browsers to redirect to attacker-controlled sites when opening the shared album link. This can facilitate phishing attacks by misleading victims into providing credentials to fake login pages. The issue is fixed in immich version 2.7.3.
CVE-2026-34257 is an Open Redirect vulnerability in SAP NetWeaver Application Server ABAP that allows an unauthenticated attacker to craft a malicious URL which, if visited by a victim, redirects them to an attacker-controlled site. This vulnerability impacts confidentiality and integrity at a low level and does not affect availability. It affects multiple SAP_BASIS versions from 700 through 816. The CVSS score is 6.1, indicating a medium severity. There is no vendor advisory or patch information available at this time, and no known exploits in the wild have been reported.
The User Registration & Membership plugin for WordPress is vulnerable to Open Redirect in versions up to and including 5.1.4. This is due to insufficient validation of user-supplied URLs passed via the 'redirect_to_on_logout' GET parameter before redirecting users. The `redirect_to_on_logout` GET parameter is passed directly to WordPress's `wp_redirect()` function instead of the domain-restricted `wp_safe_redirect()`. While `esc_url_raw()` is applied to sanitize malformed URLs, it does not restrict the redirect destination to the local domain, allowing an attacker to craft a specially formed link that redirects users to potentially malicious external URLs after logout, which could be used to facilitate phishing attacks.
ChurchCRM is an open-source church management system. Prior to 7.0.0, it was possible in many places across the ChurchCRM application to create a link that, when visited by an authenticated user, would redirect them to any URL chosen by an attacker if they clicked 'Cancel' button on the page. For this write-up the DonatedItemEditor.php will be used as an example, however wherever all instances of 'linkBack' should be assessed. This vulnerability is fixed in 7.0.0.
Chamilo LMS is a learning management system. Prior to 1.11.38 and 2.0.0-RC.3, an Open Redirect vulnerability in the session course edit page allows an attacker to redirect an authenticated administrator to an arbitrary external URL after saving coach assignment changes. The redirect also leaks the id_session parameter to the attacker's server. This vulnerability is fixed in 1.11.38 and 2.0.0-RC.3.