Authenticated SSRF via unguarded attachment URL fetch
Published Aug 12, 2026 · Updated Aug 12, 2026
Server-side request forgery in Budibase before 3.39.4 allows remote authenticated users to read internal resources via attachment URLs. The uploadUrl function passes string attachment values from AI-generated rows to a bare server-side fetch and stores the response without fetchWithBlacklist validation. Builder access and the AI table-generation feature are required; exposed data can include internal service responses or cloud metadata.
Summary
What happened
Server-side request forgery in Budibase before 3.39.4 allows remote authenticated users to read internal resources via attachment URLs. The uploadUrl function passes string attachment values from AI-generated rows to a bare server-side fetch and stores the response without fetchWithBlacklist validation. Builder access and the AI table-generation feature are required; exposed data can include internal service responses or cloud metadata.
The record
- CVE
- CVE-2026-73307
- Published
- Aug 12, 2026
- Updated
- Aug 12, 2026
- Vendor
- Budibase
- Product
- Budibase
- Classifications
- CWE-918, T1552.005
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 12, 2026CVE publishedPublication date reported by the CVE source.
- Aug 12, 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.4
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
- GitHub advisory 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