{"answers":{"affected":"2 open source packages ship an affected version, including nocodb.","exploited":"There is no known exploitation of CVE-2026-47380 in the wild and no public exploit code.","fix":"Upgrade nocodb to 2026.04.1 or later.","what":"CVE-2026-47380 is a medium-severity vulnerability in nocodb, published on 23 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-47380 and fix it if it is affected.\n\nWhat it is: CVE-2026-47380 is a medium-severity vulnerability in nocodb, published on 23 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-47380 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- nocodb (npm): affected all versions; fixed in 2026.04.1\n- nocodb (npm): affected all versions; fixed in 2026.04.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-47380/ (Markdown: https://insights.sbomify.com/CVE-2026-47380/index.md)","id":"CVE-2026-47380","markdown":"https://insights.sbomify.com/CVE-2026-47380/index.md","name":"CVE-2026-47380","record":{"aliases":["GHSA-jr54-jwhj-55gp"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"NocoDB database platform","requires_auth":"none","summary":"Attackers can enumerate valid user accounts by analyzing sign-in response timing differences, potentially aiding targeted attacks.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.3,"severity":"medium","source":"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","version":"4.0"},"cwes":[{"id":"CWE-307","name":"Improper Restriction of Excessive Authentication Attempts"},{"id":"CWE-208","name":"Observable Timing Discrepancy"}],"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.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"NocoDB: User Enumeration via Sign-In Timing","id":"CVE-2026-47380","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":2,"n_references":1,"next":{"headline":"NocoDB: Cross-Workspace Integration Use in Connection Test","id":"CVE-2026-47381"},"packages":[{"ecosystem":"npm","fixed":["2026.04.1"],"introduced":["0"],"last_affected":[],"package":"nocodb","purl":null,"source":"GHSA-jr54-jwhj-55gp"},{"ecosystem":"npm","fixed":["2026.04.1"],"introduced":["0"],"last_affected":[],"package":"nocodb","purl":"pkg:npm/nocodb","source":"GHSA-jr54-jwhj-55gp"}],"prev":{"headline":"NocoDB: Plaintext Password Comparison in Shared Views","id":"CVE-2026-47379"},"products":["nocodb"],"published":"2026-06-23","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-24","vendors":["nocodb"]},"summary":"Attackers can enumerate valid user accounts by analyzing sign-in response timing differences, potentially aiding targeted attacks.","url":"https://insights.sbomify.com/CVE-2026-47380/"}