CVE-2026-54353
Received Received - Intake
SSRF via DNS Rebinding in Budibase

Publication date: 2026-06-26

Last updated on: 2026-06-26

Assigner: GitHub, Inc.

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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-06-26
Last Modified
2026-06-26
Generated
2026-06-27
AI Q&A
2026-06-27
EPSS Evaluated
N/A
NVD
CVE-2026-54353
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
budibase budibase to 3.39.9 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-918 The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.
CWE-367 The product checks the state of a resource before using that resource, but the resource's state can change between the check and the use in a way that invalidates the results of the check.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

This vulnerability affects Budibase, an open-source low-code platform, in versions prior to 3.39.9. Authenticated users with automation permissions can bypass Budibase's SSRF (Server-Side Request Forgery) blacklist by exploiting DNS rebinding. The system validates hostnames against a blacklist before sending requests, but the actual network connection performs a separate DNS lookup. Because the IP addresses validated are not fixed to the connection, an attacker can provide a hostname that resolves to a public IP during validation and then to a private or internal IP during the real connection. This allows attackers to perform SSRF attacks on internal services accessible from the Budibase host, including loopback addresses, private IP ranges defined by RFC1918, and cloud metadata endpoints.

Impact Analysis

This vulnerability can allow an attacker with certain permissions to access internal services that are normally protected from external access. By exploiting the SSRF flaw, attackers can potentially retrieve sensitive information from internal endpoints such as cloud metadata services or internal network resources. This can lead to unauthorized information disclosure, partial compromise of the system's confidentiality, and potentially further attacks leveraging internal network access.

Mitigation Strategies

To mitigate this vulnerability, you should upgrade Budibase to version 3.39.9 or later, where the issue is fixed.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-54353. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart