Summary
The shared-view password check fell back to strict-equality (===) comparison for
legacy plaintext passwords, leaking the password's length and per-character prefix
through response timing.
Details
The bcrypt branch (hashes starting with $2a$/$2b$) was unaffected. The legacy
fallback in View.ts now uses crypto.timingSafeEqual and a same-length dummy
compare on the length-mismatch path, so total comparison time is approximately
length-independent. The EE dashboard model's verifyPassword is patched the same way.
Credit
This issue was reported by @Proscan-one.
Impact
A network-positioned attacker could mount a timing oracle against shared views whose
passwords predated the bcrypt migration. Exploitation requires the ability to time
shared-view authentication responses but no prior authentication.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2026-47379? CVE-2026-47379 is a medium-severity security vulnerability in nocodb (npm), affecting versions <= 2026.05.0. It is fixed in 2026.05.1.
- Which versions of nocodb are affected by CVE-2026-47379? nocodb (npm) versions <= 2026.05.0 is affected.
- Is there a fix for CVE-2026-47379? Yes. CVE-2026-47379 is fixed in 2026.05.1. Upgrade to this version or later.
- Is CVE-2026-47379 exploitable, and should I be worried? Whether CVE-2026-47379 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-47379 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-47379? Upgrade
nocodbto 2026.05.1 or later.