Authenticated internal-service reads via unvalidated file URL
Published May 27, 2026 · Updated May 27, 2026
SSRF in Budibase before 3.34.8 allows remote authenticated users to read responses from internal services through the AI Extract File step. The processUrlFile function in packages/server/src/automations/steps/ai/extract.ts passes a supplied fileUrl directly to fetch instead of fetchWithBlacklist. Builder permissions and an AI Extract File automation using URL input are required; the server can expose cloud metadata, internal APIs, or network-service responses.
Summary
What happened
SSRF in Budibase before 3.34.8 allows remote authenticated users to read responses from internal services through the AI Extract File step. The processUrlFile function in packages/server/src/automations/steps/ai/extract.ts passes a supplied fileUrl directly to fetch instead of fetchWithBlacklist. Builder permissions and an AI Extract File automation using URL input are required; the server can expose cloud metadata, internal APIs, or network-service responses.
The record
- CVE
- CVE-2026-45548
- Published
- May 27, 2026
- Updated
- May 27, 2026
- Vendor
- Budibase
- Product
- Budibase
- Classifications
- CWE-918, T1046, 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.34.8
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
- Vendor advisory reproduction stepsproof 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