Budibase Server before 3.41.3 SSRF with Credential Leakage

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Affected scope and exposure questions

The current feed maps budibase/server (generic). Check affected ranges and fixed versions before updating.

Recommended response

1. 1Check inventory. Check lockfiles and deployed manifests for budibase/server.
2. 2Review the reported fix. Update budibase/server to 3.41.3 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

1. Published upstream

   Aug 28, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

2. Source modified

   Aug 28, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

3. First seen by HOL

   Aug 28, 2026

Sources and claim methodology

• GitHub security advisorygithub.com
• Source referencevulncheck.com

Related CVEs

• Budibase before 3.41.3 Authorization Bypass via datasources/querySame budibase/server package
• Budibase before 3.41.3 Privilege Escalation via User Update APISame budibase/server package
• Budibase backend-core SSRF via incomplete default blacklistSame budibase/server package
• Budibase before 3.41.3 Cross-Application Resource Injection via Missing AuthorizationSame budibase/server package
• Budibase before 3.41.3 Remote Code Execution via Plugin eval()Same budibase/server package
• Budibase before 3.41.3 Missing Authorization License ManagementSame budibase/server package