<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Cve-2026-45715 — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/tags/cve-2026-45715/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Fri, 15 May 2026 17:54:56 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/tags/cve-2026-45715/feed.xml" rel="self" type="application/rss+xml"/><item><title>Budibase REST Datasource SSRF via HTTP Redirect Bypass (CVE-2026-45715)</title><link>https://feed.craftedsignal.io/briefs/2026-05-budibase-ssrf/</link><pubDate>Fri, 15 May 2026 17:54:56 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-05-budibase-ssrf/</guid><description>Budibase is vulnerable to server-side request forgery (SSRF) via HTTP redirects in the REST datasource integration, allowing authenticated Builders to bypass IP blacklists and access internal services.</description><content:encoded><![CDATA[<p>Budibase is susceptible to a server-side request forgery (SSRF) vulnerability within its REST datasource integration. This flaw allows an authenticated &ldquo;Builder&rdquo; user to bypass the built-in IP blacklist and access internal network resources. The vulnerability stems from the <code>_req()</code> method in <code>packages/server/src/integrations/rest.ts</code> not re-checking the IP blacklist after an HTTP redirect, an oversight previously addressed in the automation steps (<code>fetchWithBlacklist</code> in <code>packages/server/src/automations/steps/utils.ts</code>). By setting up an attacker-controlled server to redirect requests to internal services or cloud metadata endpoints, an attacker can steal sensitive information. This issue was confirmed on Budibase v3.34.6, with a fix released in version 3.38.1. This poses a significant risk to cloud environments where Budibase instances are deployed, as it can lead to credential theft and unauthorized access to internal resources.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>The attacker sets up a redirect server (e.g., using Python&rsquo;s <code>http.server</code>) on a publicly accessible IP address, configured to redirect to an internal service or cloud metadata endpoint.</li>
<li>An authenticated &ldquo;Builder&rdquo; user in Budibase creates a REST datasource, configuring it to point to the attacker&rsquo;s redirect server.</li>
<li>The Builder initiates a query using the newly created REST datasource. The request includes the attacker&rsquo;s server URL in the <code>path</code> field of the query configuration.</li>
<li>Budibase&rsquo;s <code>_req()</code> method in <code>packages/server/src/integrations/rest.ts</code> performs an initial IP blacklist check on the attacker&rsquo;s server URL. Because the attacker&rsquo;s server is public, this check passes.</li>
<li>The <code>fetch()</code> function follows the HTTP redirect (301/302/307) to the internal target specified by the attacker&rsquo;s server (e.g., <code>http://169.254.169.254/latest/meta-data/iam/security-credentials/</code>). Critically, this redirect is NOT re-checked against the IP blacklist.</li>
<li>The request is sent to the internal target, bypassing the intended security control.</li>
<li>The internal target (e.g., cloud metadata service) responds with sensitive information.</li>
<li>Budibase receives the response from the internal target and displays it to the Builder user, effectively leaking sensitive information like cloud IAM credentials or allowing access to internal services.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>The vulnerability allows attackers to bypass the IP blacklist and access internal services, leading to potential data breaches. On cloud instances, attackers can steal IAM credentials from metadata endpoints like <code>169.254.169.254</code>. Successful exploitation enables access to internal services such as CouchDB (<code>:4005</code>), Redis (<code>:6379</code>), and MinIO (<code>:4004</code>). This SSRF vulnerability was previously fixed in automation steps (commits <code>6cfa3bcca3</code>, <code>e7d47625be</code>) but not in the REST datasource integration, highlighting a critical oversight.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade Budibase to version 3.38.1 or later to patch CVE-2026-45715.</li>
<li>Deploy the Sigma rule &ldquo;Detect Budibase SSRF via REST Datasource to Metadata Endpoint&rdquo; to detect exploitation attempts targeting cloud metadata endpoints.</li>
<li>Deploy the Sigma rule &ldquo;Detect Budibase SSRF via REST Datasource Redirect&rdquo; to detect exploitation attempts redirecting to internal services.</li>
<li>Review and audit existing REST datasource configurations for any suspicious URLs that may point to external or unexpected internal targets.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>ssrf</category><category>budibase</category><category>cve-2026-45715</category></item></channel></rss>