CVE-2026-24768

An unvalidated redirect (open redirect) vulnerability exists in NocoDB’s login flow due to missing validation of the continueAfterSignIn parameter.

During authentication, NocoDB processes a user-controlled redirect value and conditionally performs client-side navigation without enforcing any restrictions on the destination’s origin, domain or protocol. This allows attackers to redirect authenticated users to arbitrary external websites after login.

Root Cause

The redirect logic relies on a permissive URL check that treats any absolute or protocol-relative URL as safe, and performs navigation without applying an allowlist or origin validation.

In the redirect plugin:

• The helper function isFullUrl uses the following regular expression:

  /^(https?:)?\/\//
  

  This pattern matches any HTTP(S) URL as well as protocol-relative URLs (e.g., //evil.example), without restricting allowed domains.

• When the continueAfterSignIn query parameter matches this pattern, the application performs an unconditional external navigation:

  navigateTo(route.value.query.continueAfterSignIn as string, {
    external: isFullUrl(...)
  })
  

Attack Scenario

An attacker can exploit this issue through a phishing attack:

1. The attacker crafts a malicious login URL containing a controlled redirect target, for example:

   https://victim-nocodb.example/#/signin?continueAfterSignIn=https://evil-phishing.com/fake-login
   

2. The victim clicks the link and is presented with the legitimate NocoDB login page.

3. The victim authenticates using valid credentials.

4. After login, NocoDB automatically redirects the victim to the attacker-controlled external site.

5. The attacker’s site displays a fake error message and prompts the victim to re-enter credentials.

6. The victim unknowingly submits credentials to the attacker.

Credit

This issue was discovered by an AI agent developed by the GitHub Security Lab and reviewed by GHSL team members @p- (Peter Stöckli) and @m-y-mo (Man Yue Mo).

This vulnerability enables phishing attacks by leveraging user trust in the legitimate NocoDB login flow. While it does not directly expose credentials or bypass authentication, it increases the likelihood of credential theft through social engineering.

The issue does not allow arbitrary code execution or privilege escalation, but it undermines authentication integrity.

Untrusted input controls a URL used for redirection, which can forward users to attacker-controlled sites. Typical impact: phishing and credential harvesting via a trusted domain.

Kodem intelligence

1. What is CVE-2026-24768? CVE-2026-24768 is a medium-severity open redirect vulnerability in nocodb (npm), affecting versions < 0.301.0. It is fixed in 0.301.0. Untrusted input controls a URL used for redirection, which can forward users to attacker-controlled sites.
2. Which versions of nocodb are affected by CVE-2026-24768? nocodb (npm) versions < 0.301.0 is affected.
3. Is there a fix for CVE-2026-24768? Yes. CVE-2026-24768 is fixed in 0.301.0. Upgrade to this version or later.
4. Is CVE-2026-24768 exploitable, and should I be worried? Whether CVE-2026-24768 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
5. What actually determines whether CVE-2026-24768 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
6. How do I fix CVE-2026-24768? Upgrade nocodb to 0.301.0 or later.