{"answers":{"affected":"2 open source packages ship an affected version, including @budibase/backend-core. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54353 exists.","fix":"Upgrade @budibase/backend-core to 3.39.9 or later.","what":"CVE-2026-54353 is a high-severity server-side request forgery vulnerability in budibase, published on 26 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-54353 and fix it if it is affected.\n\nWhat it is: CVE-2026-54353 is a high-severity server-side request forgery vulnerability in budibase, published on 26 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54353 exists.\n\nAffected packages and fixed versions:\n- @budibase/backend-core (npm): affected all versions; fixed in 3.39.9\n- @budibase/backend-core (npm): affected all versions; fixed in 3.39.9\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-54353/ (Markdown: https://insights.sbomify.com/CVE-2026-54353/index.md)","id":"CVE-2026-54353","markdown":"https://insights.sbomify.com/CVE-2026-54353/index.md","name":"CVE-2026-54353","record":{"aliases":["GHSA-gfq7-5x4g-3xhf"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Budibase low-code platform","requires_auth":"low_privilege","summary":"Authenticated users with automation permissions can bypass SSRF protections via DNS rebinding to access internal services and cloud metadata.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"budibase","vendor":"budibase"}],"cvss":{"score":8.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"},{"id":"CWE-367","name":"Time-of-check Time-of-use (TOCTOU) Race Condition"}],"description":"Budibase is an open-source low-code platform. Prior to 3.39.9, authenticated users with automation permissions can bypass Budibase's SSRF blacklist through DNS rebinding. The outbound fetch flow validates a hostname against the blacklist before the request is sent, but the actual socket connection later performs a separate DNS lookup through node-fetch. Since the validated IPs are never pinned to the connection, an attacker-controlled hostname can return a public IP during validation and a private/internal IP during the real connection. This results in a non-blind SSRF primitive against internal services reachable from the Budibase host, including loopback, RFC1918 ranges, and cloud metadata endpoints. This vulnerability is fixed in 3.39.9.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Budibase: Potential SSRF DNS rebinding bypass in outbound fetch validation","id":"CVE-2026-54353","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":2,"n_references":1,"next":{"headline":"MapServer: PostGIS Numeric Filter Value SQL Injection in MapServer Runtime Query Translation","id":"CVE-2026-54354"},"packages":[{"ecosystem":"npm","fixed":["3.39.9"],"introduced":["0"],"last_affected":[],"package":"@budibase/backend-core","purl":null,"source":"GHSA-gfq7-5x4g-3xhf"},{"ecosystem":"npm","fixed":["3.39.9"],"introduced":["0"],"last_affected":[],"package":"@budibase/backend-core","purl":"pkg:npm/%40budibase/backend-core","source":"GHSA-gfq7-5x4g-3xhf"}],"prev":{"headline":"Budibase: Arbitrary file read by workspace-builder via PWA-zip symlink upload","id":"CVE-2026-54352"},"products":["budibase"],"published":"2026-06-26","related":[{"cvss_score":10,"headline":"Budibase: Anonymous NoSQL operator injection via published-app query templates","id":"CVE-2026-54350","kev_date_added":null,"published":"2026-06-26"},{"cvss_score":9.9,"headline":"Budibase Vulnerable to Remote Code Execution via Unsafe eval() in View Filter Map Function (Budibase Cloud)","id":"CVE-2026-27702","kev_date_added":null,"published":"2026-02-25"},{"cvss_score":9.6,"headline":"Budibase: Arbitrary file read by workspace-builder via PWA-zip symlink upload","id":"CVE-2026-54352","kev_date_added":null,"published":"2026-06-26"},{"cvss_score":9.6,"headline":"Budibase: Server-Side Request Forgery via REST Connector with Empty Default Blacklist","id":"CVE-2026-31818","kev_date_added":null,"published":"2026-04-03"},{"cvss_score":9.6,"headline":"Budibase PWA ZIP Upload Path Traversal Allows Reading Arbitrary Server Files Including All Environment Secrets","id":"CVE-2026-30240","kev_date_added":null,"published":"2026-03-09"},{"cvss_score":9.1,"headline":"Budibase: Authentication Bypass via Unanchored Regex in Public Endpoint Matcher — Unauthenticated Access to Protected Endpoints","id":"CVE-2026-41428","kev_date_added":null,"published":"2026-04-24"},{"cvss_score":9.1,"headline":"Budibase: Unauthenticated Remote Code Execution via Webhook Trigger and Bash Automation Step","id":"CVE-2026-35216","kev_date_added":null,"published":"2026-04-03"}],"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":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-29","vendors":["Budibase"]},"summary":"Authenticated users with automation permissions can bypass SSRF protections via DNS rebinding to access internal services and cloud metadata.","url":"https://insights.sbomify.com/CVE-2026-54353/"}