Authenticated SSRF via unchecked OAuth2 token URL
Published May 27, 2026 · Updated May 27, 2026
SSRF in Budibase before 3.39.0 allows remote authenticated users with builder access to read internal responses via an OAuth2 URL. The OAuth2 SDK fetchToken function sends a POST to a builder-supplied URL with node-fetch without calling blacklist.isBlacklisted, and redirects are followed without revalidation. Builder access is required; the server can reach internal services or cloud metadata and expose response fragments, tenant data, or instance credentials.
Summary
What happened
SSRF in Budibase before 3.39.0 allows remote authenticated users with builder access to read internal responses via an OAuth2 URL. The OAuth2 SDK fetchToken function sends a POST to a builder-supplied URL with node-fetch without calling blacklist.isBlacklisted, and redirects are followed without revalidation. Builder access is required; the server can reach internal services or cloud metadata and expose response fragments, tenant data, or instance credentials.
The record
- CVE
- CVE-2026-48153
- Published
- May 27, 2026
- Updated
- May 27, 2026
- Vendor
- Budibase
- Product
- Budibase
- Classifications
- CWE-918, T1552.005
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 27, 2026CVE publishedPublication date reported by the CVE source.
- May 27, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 3.39.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GHSA-4q6h-8p4v-67vq proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo