{"answers":{"affected":"2 open source packages ship an affected version, including nocodb.","exploited":"There is no known exploitation of CVE-2026-53931 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-53931 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-53931 is a medium-severity server-side request forgery 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-53931 and fix it if it is affected.\n\nWhat it is: CVE-2026-53931 is a medium-severity server-side request forgery 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-53931 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-53931/ (Markdown: https://insights.sbomify.com/CVE-2026-53931/index.md)","id":"CVE-2026-53931","markdown":"https://insights.sbomify.com/CVE-2026-53931/index.md","name":"CVE-2026-53931","record":{"aliases":["GHSA-hmcr-rmjq-47qr"],"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":"none","summary":"Unauthenticated attackers can exploit a flawed URL validation in the spreadsheet import endpoint to perform Server-Side Request Forgery, potentially accessing internal resources.","user_interaction":"not_required","vuln_class":"ssrf"},"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:N/VI:N/VA:N/SC:L/SI:L/SA:N","version":"4.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"},{"id":"CWE-441","name":"Unintended Proxy or Intermediary"}],"description":"NocoDB is software for building databases as spreadsheets. Prior to 2026.05.1, the spreadsheet-import endpoint axiosRequestMake could be used as a generic HTTP proxy. Before the fix it was reachable unauthenticated, and its URL-extension allowlist was a regex tested against the full URL string, so URLs whose query string ended in .csv satisfies the gate even though the\nunderlying request is for another file. 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 Spreadsheet Import Endpoint","id":"CVE-2026-53931","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":2,"n_references":1,"next":{"headline":"laravel-backup-restore has an OS Command Injection during database restore","id":"CVE-2026-53932"},"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["0.301.3"],"package":"nocodb","purl":null,"source":"GHSA-hmcr-rmjq-47qr"},{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["0.301.3"],"package":"nocodb","purl":"pkg:npm/nocodb","source":"GHSA-hmcr-rmjq-47qr"}],"prev":{"headline":"NocoDB: Server-Side Request Forgery via Base Migration URL","id":"CVE-2026-53930"},"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":"Unauthenticated attackers can exploit a flawed URL validation in the spreadsheet import endpoint to perform Server-Side Request Forgery, potentially accessing internal resources.","url":"https://insights.sbomify.com/CVE-2026-53931/"}