CVE-2026-48153 Budibase: SSRF via OAuth2 token endpoint URL reaches internal hosts and cloud metadata
Attackers can exploit missing URL validation in Budibase's OAuth2 token endpoint to access internal network resources and cloud metadata.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-48153?
CVE-2026-48153 is a high-severity server-side request forgery vulnerability in budibase, published on 27 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
Budibase is an open-source low-code platform. Prior to 3.39.0, fetchToken in the OAuth2 SDK makes a POST to a builder-supplied URL with plain node-fetch, skipping the blacklist.isBlacklisted check that every other outbound fetch path in the codebase uses. The Joi schema for the OAuth2 URL has no scheme or host restriction. This vulnerability is fixed in 3.39.0.
Weakness: CWE-918
Which versions are affected by CVE-2026-48153?
2 open source packages ship an affected version, including @budibase/server.
| Package | Affected | Fixed in |
|---|---|---|
@budibase/server npm | All versions | 3.39.0 |
@budibase/server npm | All versions | 3.39.0 |
How do I fix CVE-2026-48153?
Upgrade @budibase/server to 3.39.0 or later.
Upgrade, and send outbound requests through an allow-list that blocks internal addresses. More about Server-side request forgery.
Is CVE-2026-48153 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-48153 exists.
Sources
Also known as GHSA-4q6h-8p4v-67vq.