# CVE-2026-54353: Budibase: Potential SSRF DNS rebinding bypass in outbound fetch validation > Authenticated users with automation permissions can bypass SSRF protections via DNS rebinding to access internal services and cloud metadata. - **Severity:** High 8.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 26 Jun 2026 - **Updated:** 29 Jun 2026 - **Also known as:** GHSA-gfq7-5x4g-3xhf ## What is CVE-2026-54353? 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. ### Official 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. Weakness: CWE-918 (Server-Side Request Forgery), CWE-367 (Time-of-check Time-of-use (TOCTOU) Race Condition) ## Which versions are affected by CVE-2026-54353? 2 open source packages ship an affected version, including @budibase/backend-core. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `@budibase/backend-core` | npm | All versions | 3.39.9 | | `@budibase/backend-core` | npm | All versions | 3.39.9 | Products: Budibase Budibase. ## How do I fix CVE-2026-54353? Upgrade @budibase/backend-core to 3.39.9 or later. ## Is CVE-2026-54353 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54353 exists. ## Other vulnerabilities in budibase - [CVE-2026-54350](https://insights.sbomify.com/CVE-2026-54350/): Budibase: Anonymous NoSQL operator injection via published-app query templates (critical 10.0) - [CVE-2026-27702](https://insights.sbomify.com/CVE-2026-27702/): Budibase Vulnerable to Remote Code Execution via Unsafe eval() in View Filter Map Function (Budibase Cloud) (critical 9.9) - [CVE-2026-54352](https://insights.sbomify.com/CVE-2026-54352/): Budibase: Arbitrary file read by workspace-builder via PWA-zip symlink upload (critical 9.6) - [CVE-2026-31818](https://insights.sbomify.com/CVE-2026-31818/): Budibase: Server-Side Request Forgery via REST Connector with Empty Default Blacklist (critical 9.6) - [CVE-2026-30240](https://insights.sbomify.com/CVE-2026-30240/): Budibase PWA ZIP Upload Path Traversal Allows Reading Arbitrary Server Files Including All Environment Secrets (critical 9.6) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-54353 and fix it if it is affected. What 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. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54353 exists. Affected packages and fixed versions: - @budibase/backend-core (npm): affected all versions; fixed in 3.39.9 - @budibase/backend-core (npm): affected all versions; fixed in 3.39.9 Task: 1. 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. 2. 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. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-54353/ (Markdown: https://insights.sbomify.com/CVE-2026-54353/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-54353 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-54353 - OSV: https://osv.dev/vulnerability/CVE-2026-54353 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-54353/ Summaries are generated and may contain mistakes; the official description above is the record.