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.
CVE-2026-47380
This medium-severity CVE scores 6.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 90% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.3
- EG Score
- 6.3(medium)
- EPSS
- 9.6%
- KEV
- Not listed
Published
June 5, 2026
Last Modified
June 25, 2026
Advisory Details (1)
Auto-updated Jun 25, 2026User Enumeration via Sign-In Timing · Advisory · nocodb/nocodb · GitHub
https://github.com/nocodb/nocodb/security/advisories/GHSA-jr54-jwhj-55gpVendor Advisories for CVE-2026-47380(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
npm(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| nocodb | — | 2026.04.1 | — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 12× in last 7d / 31× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 20:31 UTCEG score recompute
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 20:40 UTCEG score recompute
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-03 18:37 UTCEG score recompute
- 2026-07-02 18:13 UTCEG score recompute
- 2026-07-01 18:09 UTCEG score recompute
- 2026-07-01 15:07 UTCEPSS rescore
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-30 18:10 UTCEG score recompute
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-29 12:36 UTCEG score recompute
- 2026-06-28 14:07 UTCEPSS rescore
- 2026-06-28 12:44 UTCEG score recompute
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-27 12:54 UTCEG score recompute
- 2026-06-27 03:08 UTCEPSS rescore
- 2026-06-26 13:03 UTCEG score recompute
- 2026-06-25 13:49 UTCEPSS rescore
- 2026-06-25 11:56 UTCEG score recompute
- 2026-06-24 14:05 UTCEPSS rescore
Show 7 moreShow fewer
- 2026-06-24 12:05 UTCEG score recompute▲ 6.30
- 2026-06-24 12:01 UTCNVD updateCVSS v3 → 6.3 · CVSS v4 → 6.3 · severity → MEDIUM
- 2026-06-15 08:50 UTCEG score recompute
- 2026-06-14 23:18 UTCEPSS rescore
- 2026-06-13 23:00 UTCEPSS rescore
- 2026-06-12 23:12 UTCEPSS rescore
- 2026-06-05 16:57 UTCEG score recompute
Frequently asked(5)
What is CVE-2026-47380?
When was CVE-2026-47380 disclosed?
Is CVE-2026-47380 actively exploited?
What is the CVSS score of CVE-2026-47380?
How do I remediate CVE-2026-47380?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-47380
Is Your Infrastructure Affected by CVE-2026-47380?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.