dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2026-45061

HIGH · 7.7 CVSS v3.1 Published 2026-05-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
83/100
Remediation priority · High
Remotely reachable Zero-click

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 · unedited
Budibase is an open-source low-code platform. Prior to 3.35.10, the Plugin URL upload endpoint (POST /api/plugin) validates the submitted URL with a single substring check: url.includes(".tar.gz"). Any URL containing .tar.gz anywhere in the string — in the path, query string, or fragment — passes this check. The URL then proceeds directly to fetchWithBlacklist() with no further validation of host, scheme, or path. Standalone, this vulnerability is blocked by Budibase's default SSRF blacklist, which covers private IP ranges. But the URL validation layer itself is broken regardless, and it directly enables SSRF in two realistic situations: (1) when chained with the BLACKLIST_IPS bypass ([001]), where the blacklist is empty; and (2) when the plugin server follows HTTP redirects from an external URL to an internal target (the default node-fetch behavior with redirect: 'follow'). This vulnerability is fixed in 3.35.10.

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 confidence

The Plugin URL upload endpoint (POST /api/plugin) uses a flawed substring check (url.includes(".tar.gz")) that accepts any URL containing ".tar.gz" anywhere without validating host, scheme, or path. This enables SSRF by bypassing blacklist protections through empty IP blacklists or HTTP redirect following to internal targets.

MitigationUpgrade Budibase to version 3.35.10 or later which implements proper URL validation before fetching.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Budibase version
    Check the installed Budibase version through the admin UI (Settings > About), environment variables (check for APP_VERSION or similar), or the Docker/container image tag if running in containers
    Affected if Version is present and below 3.35.10
  2. Compare version to fixed release
    Review the identified version against 3.35.10 - any version lower than 3.35.10 contains the vulnerable substring check
    Affected if Installed version is below 3.35.10
  3. Verify plugin upload endpoint exists
    Confirm the /api/plugin endpoint is available by checking if plugin upload functionality exists in the Budibase installation - typically accessible through the admin portal or via API availability
    Affected if The endpoint exists and is accessible (no authentication or weak authentication allows access)
  4. Confirm network accessibility
    Assess whether the Budibase server can make outbound HTTP/HTTPS requests to internal network targets - check firewall rules, network policies, and whether the server has access to internal IP ranges or services
    Affected if Server can reach internal network resources via HTTP redirects, enabling SSRF exploitation

A Budibase installation is affected if it runs a version below 3.35.10 and has the plugin upload endpoint accessible, as the flawed url.includes(".tar.gz") check would allow SSRF via malicious URLs.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Budibase to version 3.35.10 or later which implements proper URL validation before fetching.

Recommended fix High confidence

3.35.10

  1. 1. Identify all Budibase installations currently running versions prior to 3.35.10
  2. 2. Review current configuration to check if BLACKLIST_IPS is set (empty blacklist would increase exposure)
  3. 3. Plan maintenance window for upgrade
  4. 4. Backup current Budibase configuration and data
  5. 5. Upgrade Budibase to version 3.35.10 or later
  6. 6. Verify the upgrade was successful by checking the Budibase version
  7. 7. Test the plugin upload functionality to confirm the fix works properly
  8. 8. Monitor logs for any attempted exploitation attempts

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-45061 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-45061 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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