How severe is CVE-2026-47380?

CVE-2026-47380 has a CVSS 4.0 base score of 6.3, rated medium severity.

Is CVE-2026-47380 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (22nd percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2026-47380?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

Does CVE-2026-47380 have an EU (EUVD) identifier?

Yes. CVE-2026-47380 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-38624.

When was CVE-2026-47380 published?

CVE-2026-47380 was published on 2026-06-23 and last updated on 2026-06-25.

CVE-2026-47380

CVE-2026-47380 is a medium-severity vulnerability with a CVSS 4.0 base score of 6.3. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-208.

Key facts

Severity: Medium (CVSS 4.0 base score 6.3)
EPSS exploit prediction: 0% (22nd percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2026-38624
Weakness: CWE-208
Published: 2026-06-23
Last modified: 2026-06-25

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.

Frequently asked questions

What is CVE-2026-47380?: 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.
How severe is CVE-2026-47380?: CVE-2026-47380 has a CVSS 4.0 base score of 6.3, rated medium severity.
Is CVE-2026-47380 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (22nd percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2026-47380?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2026-47380 have an EU (EUVD) identifier?: Yes. CVE-2026-47380 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-38624.
When was CVE-2026-47380 published?: CVE-2026-47380 was published on 2026-06-23 and last updated on 2026-06-25.

References

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

Other CWE-208 vulnerabilities

CVE-2026-77987 — Critical (CVSS 9.8): A server-side request forgery (SSRF) vulnerability was identified in the notebook viewer of GitHub Enterprise Server.…
CVE-2023-41313 — Critical (CVSS 9.8): The authentication method in Apache Doris versions before 2.0.0 was vulnerable to timing attacks. Users are recommended…
CVE-2026-63132 — Critical (CVSS 9.2): OpenBao is an open source identity-based secrets management system. Prior to 2.6.0, OpenBao's handleLogicalRecovery…
CVE-2026-16315 — High (CVSS 8.7): OMICRON StationGuard before version 4.10 contains a cryptographic timing side-channel vulnerability in the backend…
CVE-2024-42512 — High (CVSS 8.6): Vulnerability in the OPC UA .NET Standard Stack before 1.5.374.158 allows an unauthorized attacker to bypass…
CVE-2026-43606 — High (CVSS 8.5): Observable Timing Discrepancy in the AMD Vitis Libraries ECDSA secp256k1 component could allow attackers with local…

Browse all CWE-208 vulnerabilities →