{"answers":{"affected":"2 open source packages ship an affected version, including nocodb.","exploited":"There is no known exploitation of CVE-2026-47385 in the wild and no public exploit code.","fix":"Upgrade nocodb to 2026.05.1 or later.","what":"CVE-2026-47385 is a medium-severity path traversal vulnerability in nocodb, published on 23 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-47385 and fix it if it is affected.\n\nWhat it is: CVE-2026-47385 is a medium-severity path traversal vulnerability in nocodb, published on 23 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-47385 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-47385/ (Markdown: https://insights.sbomify.com/CVE-2026-47385/index.md)","id":"CVE-2026-47385","markdown":"https://insights.sbomify.com/CVE-2026-47385/index.md","name":"CVE-2026-47385","record":{"aliases":["GHSA-wvqj-9wv4-7ff5"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"NocoDB database platform","requires_auth":"low_privilege","summary":"Authenticated users can exploit path traversal in SQLite source filenames to read or overwrite arbitrary files on the NocoDB host.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"NocoDB is software for building databases as spreadsheets. Prior to 2026.05.1, an authenticated user with base-create permission can attach a SQLite source pointing at an arbitrary file on the NocoDB host, including NocoDB's own internal databases. The SQLite client and the base/integration create services accepted a caller-supplied filename and passed it to fs.exists and fs.open('w') without restricting the location. A user could point a source at noco.db, at a tenant database under nc_minimal_dbs/, or at any writable path the NocoDB process can reach, and then read or overwrite its contents through the regular table APIs.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: Path Traversal via SQLite Source Filename","id":"CVE-2026-47385","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":2,"n_references":1,"next":{"headline":"NocoDB: OAuth Authorization Code Race Condition","id":"CVE-2026-47386"},"packages":[{"ecosystem":"npm","fixed":["2026.05.1"],"introduced":["0"],"last_affected":[],"package":"nocodb","purl":null,"source":"GHSA-wvqj-9wv4-7ff5"},{"ecosystem":"npm","fixed":["2026.05.1"],"introduced":["0"],"last_affected":[],"package":"nocodb","purl":"pkg:npm/nocodb","source":"GHSA-wvqj-9wv4-7ff5"}],"prev":{"headline":"NocoDB: SQL Injection via Column Title in Bulk GroupBy","id":"CVE-2026-47384"},"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":"partial"},"state":"PUBLISHED","updated":"2026-06-24","vendors":["nocodb"]},"summary":"Authenticated users can exploit path traversal in SQLite source filenames to read or overwrite arbitrary files on the NocoDB host.","url":"https://insights.sbomify.com/CVE-2026-47385/"}