# CVE-2026-46427: Budibase: Snowflake private key returned unmasked from datasource API to BASIC users

> Authenticated users can retrieve unmasked Snowflake private keys from the datasource API due to improper secret masking logic.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 May 2026
- **Updated:** 28 May 2026
- **Also known as:** GHSA-qv26-4hvj-m7fv

## What is CVE-2026-46427?

CVE-2026-46427 is a high-severity vulnerability in budibase, published on 27 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Budibase is an open-source low-code platform. Prior to 3.38.3, removeSecrets at packages/server/src/sdk/workspace/datasources/datasources.ts masks only datasource config fields whose schema type is DatasourceFieldType.PASSWORD. The Snowflake integration types its privateKey field as SENSITIVE_LONGFORM, which the filter skips. GET /api/datasources/:datasourceId lives on authorizedRoutes guarded by PermissionType.TABLE + PermissionLevel.READ. An authenticated BASIC user with any app role and call the endpoint and receive the full Snowflake PEM in plaintext. This vulnerability is fixed in 3.38.3.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-46427?


## How do I fix CVE-2026-46427?

No fix has been published for CVE-2026-46427 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-46427 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-46427 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-46427 and fix it if it is affected.

What it is: CVE-2026-46427 is a high-severity vulnerability in budibase, published on 27 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-46427 exists.

Affected product: budibase. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-46427/ (Markdown: https://insights.sbomify.com/CVE-2026-46427/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-46427
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-46427
- OSV: https://osv.dev/vulnerability/CVE-2026-46427

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-46427/
Summaries are generated and may contain mistakes; the official description above is the record.