{"answers":{"affected":"2 open source packages ship an affected version, including nocodb.","exploited":"There is no known exploitation of CVE-2026-53930 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-53930 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-53930 is a medium-severity server-side request forgery vulnerability in nocodb, published on 23 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-53930 and fix it if it is affected.\n\nWhat it is: CVE-2026-53930 is a medium-severity server-side request forgery vulnerability in nocodb, published on 23 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-53930 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- nocodb (npm): affected all versions up to 0.301.3; no fix listed\n- nocodb (npm): affected all versions up to 0.301.3; no fix listed\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-53930/ (Markdown: https://insights.sbomify.com/CVE-2026-53930/index.md)","id":"CVE-2026-53930","markdown":"https://insights.sbomify.com/CVE-2026-53930/index.md","name":"CVE-2026-53930","record":{"aliases":["GHSA-h6vv-pcq8-7xm4"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"NocoDB database tool","requires_auth":"high_privilege","summary":"Attackers can exploit the base-migration endpoint to perform Server-Side Request Forgery, accessing internal resources or arbitrary protocols.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.1,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"NocoDB is software for building databases as spreadsheets. Prior to 2026.05.1, the base-migration endpoint accepted a caller-supplied URL that the migration worker dereferenced without enforcing protocol or destination, allowing scheme abuse (file:, ftp:, etc.) and probing of internal HTTP destinations. 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":false,"headline":"NocoDB: Server-Side Request Forgery via Base Migration URL","id":"CVE-2026-53930","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":2,"n_references":1,"next":{"headline":"NocoDB: Server-Side Request Forgery via Spreadsheet Import Endpoint","id":"CVE-2026-53931"},"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["0.301.3"],"package":"nocodb","purl":null,"source":"GHSA-h6vv-pcq8-7xm4"},{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["0.301.3"],"package":"nocodb","purl":"pkg:npm/nocodb","source":"GHSA-h6vv-pcq8-7xm4"}],"prev":{"headline":"NocoDB: Stored Cross-Site Scripting via Secure Attachment","id":"CVE-2026-53929"},"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 exploit the base-migration endpoint to perform Server-Side Request Forgery, accessing internal resources or arbitrary protocols.","url":"https://insights.sbomify.com/CVE-2026-53930/"}