{"answers":{"affected":"2 open source packages ship an affected version, including nocodb.","exploited":"There is no known exploitation of CVE-2026-47381 in the wild and no public exploit code.","fix":"Upgrade nocodb to 2026.05.1 or later.","what":"CVE-2026-47381 is a medium-severity missing authorization 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-47381 and fix it if it is affected.\n\nWhat it is: CVE-2026-47381 is a medium-severity missing authorization 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-47381 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- nocodb (npm): affected all versions; fixed in 2026.05.1\n- nocodb (npm): affected all versions; fixed in 2026.05.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-47381/ (Markdown: https://insights.sbomify.com/CVE-2026-47381/index.md)","id":"CVE-2026-47381","markdown":"https://insights.sbomify.com/CVE-2026-47381/index.md","name":"CVE-2026-47381","record":{"aliases":["GHSA-96fh-m4r8-6v9v"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["security_bypass","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"NocoDB database platform","requires_auth":"none","summary":"Attackers can test integrations in other workspaces by bypassing permission checks, potentially exposing configuration details or enabling unauthorized access.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-290","name":"Authentication Bypass by Spoofing"}],"description":"NocoDB is software for building databases as spreadsheets. Prior to 2026.05.1, a user in one workspace could exercise another workspace's integration through the testConnection endpoint by supplying its ID, because the integration was fetched in a bypass scope and the caller's permission check matched any base in any workspace. This vulnerability is fixed in 2026.05.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: Cross-Workspace Integration Use in Connection Test","id":"CVE-2026-47381","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":2,"n_references":1,"next":{"headline":"NocoDB: Server-Side Request Forgery via Database Connection Host","id":"CVE-2026-47382"},"packages":[{"ecosystem":"npm","fixed":["2026.05.1"],"introduced":["0"],"last_affected":[],"package":"nocodb","purl":null,"source":"GHSA-96fh-m4r8-6v9v"},{"ecosystem":"npm","fixed":["2026.05.1"],"introduced":["0"],"last_affected":[],"package":"nocodb","purl":"pkg:npm/nocodb","source":"GHSA-96fh-m4r8-6v9v"}],"prev":{"headline":"NocoDB: User Enumeration via Sign-In Timing","id":"CVE-2026-47380"},"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":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-06-24","vendors":["nocodb"]},"summary":"Attackers can test integrations in other workspaces by bypassing permission checks, potentially exposing configuration details or enabling unauthorized access.","url":"https://insights.sbomify.com/CVE-2026-47381/"}