Is CVE-2026-48128 exploited in the wild?

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

How severe is CVE-2026-48128?

Medium severity, with a CVSS score of 4, published 27 May 2026.

Which products and versions are affected?

budibase (npm) < 3.39.0, SEMVER:introduced=0,fixed=3.39.0.

Is there a fix for CVE-2026-48128?

Yes. budibase (npm): upgrade to 3.39.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-48128 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-48128?

Check whether you run budibase (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-48128: Budibase SSRF in executeQuery automation step

Q: Which products and versions are affected?

budibase (npm) < 3.39.0, SEMVER:introduced=0,fixed=3.39.0.

Q: Is there a fix for CVE-2026-48128?

Yes. budibase (npm): upgrade to 3.39.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-48128 attacked?

It is attacked over the network, in a network appliance.

Q: Am I affected by CVE-2026-48128?

Check whether you run budibase (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-48128 · Severity: medium · CVSS 4 · Published 2026-05-27

Budibase is a low-code platform used to build internal business applications. A vulnerability in the automation engine allows users with 'builder' permissions to force the Budibase server to make unauthorized requests to internal network services. This could lead to the exposure of sensitive internal data, such as cloud infrastructure metadata, though it requires high-level access that already permits similar actions.

Technologies: budibase (npm). Vendors: npm.

Quick answers

Is CVE-2026-48128 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-48128 being exploited in the wild.
How severe is CVE-2026-48128?: Medium severity, with a CVSS score of 4, published 27 May 2026.
Which products and versions are affected?: budibase (npm) < 3.39.0, SEMVER:introduced=0,fixed=3.39.0.
Is there a fix for CVE-2026-48128?: Yes. budibase (npm): upgrade to 3.39.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-48128 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-48128?: Check whether you run budibase (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.

How to fix

budibase (npm): upgrade to 3.39.0 or later
```
npm install budibase@3.39.0
```

Technical details

A Server-Side Request Forgery (SSRF) vulnerability exists in Budibase's 'executeQuery' automation step. The component accepts a 'queryId' from user-controlled automation inputs and passes it to 'queryController.executeV2AsAutomation' without sufficient validation. An attacker with builder-level privileges can configure a REST datasource pointing to internal infrastructure (e.g., 169.254.169.254) and trigger an automation to execute a query against it. The Budibase server then performs the request from its own network context and returns the response in the automation output. This issue is mitigated by the fact that builder-level access is a prerequisite, which already grants significant control over datasources. The vulnerability is addressed in version 3.39.0.

Affected products

Budibase budibase < 3.39.0

Identifiers

CVE-2026-48128
GHSA-6964-pp88-6wp9

Timeline

2026-05-21: disclosed
2026-05-27: advisory: NVD publication
2026-06-12: patched: GitHub Advisory updated with patch information

References

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