Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦 npm

GHSA-3hmw-8mw3-rmpj

NocoDB has Unvalidated Redirect in Login Flow via continueAfterSignIn Parameter

Also known asCVE-2026-24768
Published
Jan 28, 2026
Updated
Feb 3, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed

EPSS Exploitation Probability

via FIRST.org ↗
0.3%probability of exploitation in next 30 days
Lower Risk18th percentile+0.25%
0.00%0.26%0.51%0.77%0.0%0.3%Feb 26May 26Jun 26

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

nocodbnpm
3Kdownloads / week

Description

Summary

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.

Impact

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.

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).

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmnocodball versions0.301.0

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for nocodb. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update nocodb to 0.301.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3hmw-8mw3-rmpj is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-3hmw-8mw3-rmpj is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-3hmw-8mw3-rmpj. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary 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,
O3 Security · Impact-Aware SCA

Is GHSA-3hmw-8mw3-rmpj in your dependencies?

O3 detects GHSA-3hmw-8mw3-rmpj across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.