Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 5.7amended

NocoDB has Unvalidated Redirect in Login Flow via continueAfterSignIn Parameter

CVE-2026-24768GHSA-3hmw-8mw3-rmpj

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (nocodb 0.301.0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm nocodb

    Affected
    < 0.301.0
    Fixed in
    0.301.0

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
5.7 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:P · score source
EPSS
  • CVE-2026-24768: 0.31% estimated exploitation activity in the next 30 days; percentile 23.43 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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: 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…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-3hmw-8mw3-rmpj

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-3hmw-8mw3-rmpj

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-24768

Advisory: NocoDB has Unvalidated Redirect in Login Flow via continueAfterSignIn Parameter
IDs: CVE-2026-24768, GHSA-3hmw-8mw3-rmpj
Record: https://patchnext.com/advisories/cve-2026-24768 (revision 3, source checked 26 Oct 2026, 12:41 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: nocodb 0.301.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm nocodb: affected < 0.301.0; fixed in 0.301.0

## Suggested inspection (read-only)
- `npm ls nocodb --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on nocodb.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-3hmw-8mw3-rmpj (OSV record GHSA-3hmw-8mw3-rmpj lists affected ranges: npm nocodb >=0 <0.301.0 (fixed))
- Verified: https://github.com/advisories/GHSA-3hmw-8mw3-rmpj (GitHub-reviewed advisory GHSA-3hmw-8mw3-rmpj lists affected ranges: npm nocodb >=0 <0.301.0)

Commands are suggestions: review each one before running it.

Loading voting…