# CVE-2026-46424: Budibase: Missing Cache Invalidation on Public API Role Unassignment Allows Revoked Users to Retain Privileges for Up to 1 Hour

> Revoked users retain admin or builder privileges for up to one hour due to missing cache invalidation in the public API role unassignment endpoint.

- **Severity:** Medium 4.2 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/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:** Yes
- **Published:** 27 May 2026
- **Updated:** 28 May 2026
- **Also known as:** GHSA-6vp2-6r7m-2jvx

## What is CVE-2026-46424?

CVE-2026-46424 is a medium-severity missing authorization 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.2, the public API role unassignment endpoint (POST /api/public/v1/roles/unassign) updates user documents in CouchDB but does not invalidate the corresponding Redis user cache entries. Because the authentication middleware resolves user identity and permissions from this cache (TTL: 3600 seconds), a user whose admin, builder, or app-level roles have been revoked via the public API retains those privileges for up to 1 hour. This vulnerability is fixed in 3.38.2.

Weakness: CWE-269 (Improper Privilege Management)

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

2 open source packages ship an affected version, including @budibase/backend-core.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@budibase/backend-core` | npm | All versions | 3.38.2 |
| `@budibase/backend-core` | npm | All versions | 3.38.2 |

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

Upgrade @budibase/backend-core to 3.38.2 or later.

## Is CVE-2026-46424 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-46424 is a medium-severity missing authorization 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-46424 exists.

Affected packages and fixed versions:
- @budibase/backend-core (npm): affected all versions; fixed in 3.38.2
- @budibase/backend-core (npm): affected all versions; fixed in 3.38.2

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-46424/ (Markdown: https://insights.sbomify.com/CVE-2026-46424/index.md)
```

## Sources

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

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