CVE-2026-45715
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedBudibase 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe REST datasource integration in Budibase follows HTTP redirects without re-validating the destination IP against a blacklist, allowing authenticated Builders to bypass security controls and access internal services (cloud metadata, databases) by redirecting requests through an attacker-controlled server.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Budibase installationCheck for Budibase by looking for its service running on common ports (10000, 10001) or checking for Budibase configuration files in typical installation directories such as /opt/budibase or ~/budibaseAffected if Budibase is not installed on the system
-
Determine installed Budibase versionRun command: docker ps (if using Docker) to find the budibase apps container, then inspect its version label, or check package.json in the Budibase installation directory for version fieldAffected if The installed version is earlier than 3.38.1 (vulnerable)
-
Verify REST datasource is configuredLog into Budibase admin panel, navigate to the Data section, and check if any REST API datasources are configured with URLs that could potentially redirectAffected if REST datasources are configured with external or potentially redirecting URLs
-
Check HTTP redirect behaviorTest a configured REST datasource by setting a URL that returns a 30x redirect to an internal IP address (e.g., 169.254.169.254 for cloud metadata or 127.0.0.1 for localhost services)Affected if The REST datasource follows the redirect to the internal IP without blocking it
A user is affected if they run Budibase version earlier than 3.38.1 and have REST datasources that can follow HTTP redirects to internal/internal network IP addresses
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade Budibase to version 3.38.1 or later, which implements IP blacklist re-checking on HTTP redirects. Additionally, implement network segmentation to restrict internal service access.
3.38.1
- Upgrade Budibase to version 3.38.1 or later to address the SSRF vulnerability in the REST datasource integration
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-45715 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-45715 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data