CVE-2026-45715: Budibase: SSRF Bypass via HTTP Redirect in REST Datasource Integration
Noroxi assessment
Priority: Monitor (action score 30/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.25% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Budibase budibase 3.38.1.
Low priority for now. Upgrade to Budibase budibase 3.38.1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Budibase is an open-source low-code platform. Prior to 3.38.1, the REST datasource integration (packages/server/src/integrations/rest.ts) follows HTTP redirects without re-checking the IP blacklist, allowing an authenticated Builder to access internal services (cloud metadata, databases) by redirecting through an attacker-controlled server. This vulnerability is fixed in 3.38.1.
- Published
- May 27, 2026
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 17th percentile
- CWE
- CWE-918
Report tools
Action score
30
Low priority for now.
- CVSS
- 30 / 40 · 7.7 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · GitHub_M
- 7.7
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
Budibase budibase
- < 3.38.1affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| npm | @budibase/server | before 3.38.1 | 3.38.1 |
Same product
budibase: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31816Budibase Universal Auth Bypass via Webhook Query Param Injection41Plan
- CVE-2026-54350Budibase: Anonymous NoSQL operator injection via published-app query templates39Monitor
- CVE-2026-46425Budibase: SCIM endpoints lack role-based authorization, BASIC users CRUD tenant users39Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-45061May 27, 2026 · Budibase: SSRF via trivial `.tar.gz` substring bypass in Plugin URL upload (`/api/plugin`)30Monitor
- ← EarlierCVE-2026-45548May 27, 2026 · Budibase: SSRF in AI Extract File Automation Step via Missing IP Blacklist Validation30Monitor
- Later →CVE-2026-45716May 27, 2026 · Budibase: Builder-to-Admin Privilege Escalation via onboardUsers Endpoint Without SMTP Configuration35Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Budibase budibase | 3.38.1 · description | Vendor (CNA) |
| npm:@budibase/server | 3.38.1 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-3181854 days apartBudibase: Server-Side Request Forgery via REST Connector with Empty Default Blacklist39Monitor
- CVE-2026-481530 days apartBudibase: SSRF via OAuth2 token endpoint URL reaches internal hosts and cloud metadata34Monitor
- CVE-2026-3322668 days apartBudibase Unrestricted Server-Side Request Forgery (SSRF) via REST Datasource Query Preview34Monitor
- CVE-2026-103757127 days apartBudibase before 3.41.0 SSRF via uploadUrl in AI Table Generation33Monitor
- CVE-2026-6731166 days apartBudibase before 3.38.1 SSRF Blacklist Bypass via HTTP Redirect32Monitor
- CVE-2026-455480 days apartBudibase: SSRF in AI Extract File Automation Step via Missing IP Blacklist Validation30Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
- CVE-2026-4142833 days apartBudibase: Authentication Bypass via Unanchored Regex in Public Endpoint Matcher — Unauthenticated Access to Protected Endpoints36Monitor
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-918 · Server-Side Request Forgery (SSRF)CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.