Is CVE-2026-46424 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-46424 being exploited in the wild.

How severe is CVE-2026-46424?

Medium severity, with a CVSS score of 4.2, published 27 May 2026.

Which products and versions are affected?

Budibase Backend-Core < 3.38.2; @budibase/backend-core (npm) < 3.38.2, SEMVER:introduced=0,fixed=3.38.2.

Is there a fix for CVE-2026-46424?

Yes. @budibase/backend-core (npm): upgrade to 3.38.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-46424 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-46424?

Check whether you run Budibase Backend-Core or @budibase/backend-core (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-46424: Budibase improper privilege management via missing cache invalidation

Q: Is there a fix for CVE-2026-46424?

Yes. @budibase/backend-core (npm): upgrade to 3.38.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-46424 attacked?

It is attacked over the network, in a network appliance.

Q: Am I affected by CVE-2026-46424?

Check whether you run Budibase Backend-Core or @budibase/backend-core (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-46424 · Severity: medium · CVSS 4.2 · Published 2026-05-27

Budibase is an open-source low-code platform used by businesses to build internal applications. A security flaw in the platform's public API allows users whose administrative or application-level permissions have been revoked to continue using those high-level privileges for up to one hour. This could allow a terminated employee or a user with downgraded access to continue viewing sensitive data or modifying applications during the synchronization delay.

Technologies: Budibase Backend-Core, @budibase/backend-core (npm). Vendors: Budibase, npm.

Quick answers

Is CVE-2026-46424 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-46424 being exploited in the wild.
How severe is CVE-2026-46424?: Medium severity, with a CVSS score of 4.2, published 27 May 2026.
Which products and versions are affected?: Budibase Backend-Core < 3.38.2; @budibase/backend-core (npm) < 3.38.2, SEMVER:introduced=0,fixed=3.38.2.
Is there a fix for CVE-2026-46424?: Yes. @budibase/backend-core (npm): upgrade to 3.38.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-46424 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-46424?: Check whether you run Budibase Backend-Core or @budibase/backend-core (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

@budibase/backend-core (npm): upgrade to 3.38.2 or later
```
npm install @budibase/backend-core@3.38.2
```

Technical details

A cache inconsistency exists in Budibase prior to version 3.38.2 within the public API role unassignment endpoint (POST /api/public/v1/roles/unassign). While the endpoint correctly updates user documents in CouchDB, it fails to invalidate the corresponding entries in the Redis user cache. The authentication middleware prioritizes this cache, which has a Time-To-Live (TTL) of 3600 seconds. Consequently, an attacker with a valid session whose roles (admin, builder, or app-level) are revoked via the public API can continue to perform authorized actions until the cache expires. This issue specifically affects the public API path; revocations performed via the standard Admin UI correctly trigger cache invalidation.

Affected products

Budibase Budibase < 3.38.2

Identifiers

CVE-2026-46424
GHSA-6vp2-6r7m-2jvx

Timeline

2026-05-13: patched: Fixed in version 3.38.2
2026-05-14: advisory: GitHub Security Advisory published
2026-05-27: disclosed: CVE published to NVD

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.