CVE-2026-73410 is a server-side request forgery vulnerability in Budibase affecting versions prior to 3.40.0. The flaw arises from inconsistent outbound address pinning in the REST datasource integration. In the vulnerable design, one code path validated and pinned a destination address through a Node agent, but the REST integration used an undici dispatcher obtained through a separate fetch utility, causing the HTTP client to resolve the hostname again instead of honoring the previously validated address. This discrepancy allowed a hostname that initially resolved to an allowed public address to later resolve to an internal address during request execution. An authenticated builder could exploit this behavior through DNS rebinding, causing the REST integration to connect to internal network targets after validation had already succeeded. The vulnerable request path permitted arbitrary REST methods and exposed full responses from the reached internal service.
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.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.