Server-side Request Forgery (SSRF) Affecting @budibase/server package, versions <3.35.10
Threat Intelligence
Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Server-side Request Forgery (SSRF) vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-JS-BUDIBASESERVER-16759132
- published19 May 2026
- disclosed11 May 2026
- creditjeongbeannnn
Introduced: 11 May 2026
CVE-2026-45061 (opens in a new tab)How to fix?
Upgrade @budibase/server to version 3.35.10 or higher.
Overview
@budibase/server is a Budibase Web Server
Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) in the urlUpload function. An attacker can access internal network resources and sensitive metadata by submitting a crafted URL containing .tar.gz that bypasses insufficient validation, leading the server to make requests to arbitrary endpoints. This can be exploited by users with low privileges through the /api/plugin endpoint, potentially exposing confidential information from internal services or cloud metadata endpoints.
Note:
This is only exploitable if plugin loading is enabled and, for full internal network access, if the blacklist is disabled or bypassed.
Workaround
This vulnerability can be mitigated by restricting plugin URL uploads to a specific allowlist of trusted domains and ensuring the blacklist is not disabled.