Is CVE-2026-73307 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-73307 being exploited in the wild.

How severe is CVE-2026-73307?

Medium severity, with a CVSS score of 4, published 24 July 2026.

Which products and versions are affected?

@budibase/server (npm) SEMVER:introduced=0,last_affected=3.38.1.

Is there a fix for CVE-2026-73307?

A patch was published on 2026-07-22: Version 3.40.0 released with fix Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-73307 attacked?

It is attacked over the network.

Am I affected by CVE-2026-73307?

Check whether you run @budibase/server (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-73307: Budibase SSRF via bare fetch() in AI table generation

CVE-2026-73307 · Severity: medium · CVSS 4 · Published 2026-07-24

Budibase is a low-code platform for building business applications. The AI table generation feature allows authenticated users to generate table rows using language models, including attachment columns. An attacker with builder-level access can exploit a server-side request forgery (SSRF) vulnerability in the uploadUrl() function to fetch arbitrary URLs from the server, potentially exposing internal services, cloud metadata endpoints (such as AWS IAM credentials), or other sensitive network resources.

Technologies: @budibase/server (npm). Vendors: npm.

Quick answers

Is CVE-2026-73307 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-73307 being exploited in the wild.
How severe is CVE-2026-73307?: Medium severity, with a CVSS score of 4, published 24 July 2026.
Which products and versions are affected?: @budibase/server (npm) SEMVER:introduced=0,last_affected=3.38.1.
Is there a fix for CVE-2026-73307?: A patch was published on 2026-07-22: Version 3.40.0 released with fix Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-73307 attacked?: It is attacked over the network.
Am I affected by CVE-2026-73307?: Check whether you run @budibase/server (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability exists in the uploadUrl() function (packages/server/src/utilities/fileUtils.ts) which uses a bare fetch() call without SSRF protection. During AI table generation, when the LLM generates attachment column values as URLs, the processAttachments() function calls uploadUrl() to fetch these URLs server-side without blacklist validation. An attacker can craft prompts that cause the LLM to generate internal IP addresses or cloud metadata endpoints (e.g., 169.254.169.254) as attachment URLs. The attack requires builder-level authentication and AI feature enablement. The fix replaces bare fetch() with fetchWithBlacklist(), which validates URLs against a blacklist of private/internal IP ranges before making requests, consistent with other Budibase code paths that correctly use fetchWithBlacklist().

Affected products

Budibase Budibase <3.40.0

Identifiers

CVE-2026-73307
GHSA-hfhx-w8p8-4hc7

Timeline

2026-07-24: disclosed
2026-07-22: patched: Version 3.40.0 released with fix
2026-07-24: advisory: GitHub Advisory GHSA-hfhx-w8p8-4hc7 published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.