Secuno
ENNL
Book demo

CVE-2026-42239

Budibase vulnerability

8.1 HIGHPublic exploitEPSS 0.37%
  1. Published7 May 2026

Description

Budibase is an open-source low-code platform. Prior to version 3.35.10, the budibase:auth cookie containing the JWT session token is set with httpOnly: false at packages/backend-core/src/utils/utils.ts:218. JavaScript can read this cookie via document.cookie. This means every XSS becomes a full account takeover — the attacker steals the JWT and has persistent access to the victim's account. The cookie also lacks secure: true (sent over plaintext HTTP) and sameSite attribute. This issue has been patched in version 3.35.10.

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredHigh
User interactionRequired
ScopeChanged
ConfidentialityHigh
IntegrityHigh
AvailabilityNone
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:N

Affected products

Budibase< 3.35.10

Remediation

Fixed in
Budibase≥ 3.35.10

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-355758.0
ChurchCRM is an open-source church management system. Prior to 6.5.3, a Stored…
CVE-2026-251368.1
Rucio is a software framework that provides functionality to organize, manage, and…
CVE-2025-268449.8
An issue was discovered in Znuny through 7.1.3. A cookie is set without the HttpOnly…

Frequently asked

Is CVE-2026-42239 being actively exploited?

CVE-2026-42239 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.37%.

How severe is CVE-2026-42239?

CVE-2026-42239 has a CVSS 3.1 base score of 8.1, rated high. EPSS estimates a 0.37% probability of exploitation.

Which products are affected by CVE-2026-42239?

Affected products include Budibase.

How do I fix CVE-2026-42239?

Upgrade affected software to a fixed version, for example Budibase 3.35.10 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-42239 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.