Skip to main content
Meet us at Black Hat USA 2026— Las Vegas, August 1–6Book a Meeting
Mallory
UnratedPublic exploit

Budibase SSRF blacklist bypass via DNS rebinding

IdentifiersCVE-2026-54353CWE-918

CVE-2026-54353 is a server-side request forgery vulnerability in Budibase, an open-source low-code platform, affecting versions prior to 3.39.9. In the outbound fetch flow, Budibase validates the supplied hostname against an SSRF blacklist before sending the request, but the actual network connection later performs a separate DNS resolution through node-fetch. Because the IP address validated during the initial check is not pinned to the subsequent socket connection, an attacker-controlled hostname can resolve to a benign public IP during validation and then re-resolve to a private or internal IP when the real connection is made. This DNS rebinding condition creates a TOCTOU-style blacklist bypass and yields a non-blind SSRF primitive from the Budibase host to internal services, including loopback, RFC1918 space, and cloud metadata endpoints.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows an authenticated user with automation permissions to bypass Budibase's SSRF protections and issue server-side requests to internal resources reachable from the Budibase host. This can expose sensitive internal services and data, including loopback-only services, RFC1918/private network services, Kubernetes or VPC-reachable resources, and cloud metadata endpoints such as 169.254.169.254. Depending on the environment, impact may include disclosure of internal application data, access to cloud instance metadata, and possible exposure of cloud IAM credentials where metadata hardening is not in place.

Mitigation

If you can’t patch tonight, do this now.

If immediate upgrade is not possible, restrict or disable automation features for untrusted users, especially accounts with automation permissions. Apply egress filtering from the Budibase host to block access to loopback, RFC1918/internal address space, link-local ranges, and cloud metadata endpoints where feasible. Monitor outbound requests from Budibase for suspicious access to internal services or metadata IPs. Additional defensive controls should ensure that SSRF protections validate and enforce the final resolved connection target, not only the original hostname.

Remediation

Patch, then assume compromise.

Upgrade Budibase/@budibase/backend-core to version 3.39.9 or later, which fixes the DNS rebinding-based SSRF blacklist bypass. The underlying remediation is to ensure outbound fetch validation applies to the actual destination used for the socket connection, including pinning or otherwise enforcing the validated IP at connection time rather than relying on a separate preflight hostname resolution.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
BudibaseBackend-Coreapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity8

Community discussion across Reddit, Mastodon, and other social sources.