Is CVE-2026-73409 exploited in the wild?

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

How severe is CVE-2026-73409?

Medium severity, with a CVSS score of 4, published 24 July 2026.

Which products and versions are affected?

@budibase/server (npm) SEMVER:introduced=0,last_affected=3.38.1.

Is there a fix for CVE-2026-73409?

A patch was published on 2026-07-24: Fixed in version 3.40.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-73409 attacked?

It is attacked over the network.

Am I affected by CVE-2026-73409?

Check whether you run @budibase/server (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-73409: Budibase arbitrary filesystem path read oracle in MongoDB datasource

CVE-2026-73409 · Severity: medium · CVSS 4 · Published 2026-07-24

Budibase is a low-code application platform that allows builders to create datasources by configuring connections to databases. A vulnerability in the MongoDB datasource configuration allows a builder to supply arbitrary file paths, which the server reads when verifying the connection. By observing different error messages, an attacker can determine whether files exist anywhere on the underlying server filesystem and exfiltrate their contents—potentially accessing secrets, configuration files, and other tenants' data on multi-tenant Budibase Cloud instances.

Technologies: @budibase/server (npm). Vendors: npm.

Quick answers

Is CVE-2026-73409 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-73409 being exploited in the wild.
How severe is CVE-2026-73409?: Medium severity, with a CVSS score of 4, published 24 July 2026.
Which products and versions are affected?: @budibase/server (npm) SEMVER:introduced=0,last_affected=3.38.1.
Is there a fix for CVE-2026-73409?: A patch was published on 2026-07-24: Fixed in version 3.40.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-73409 attacked?: It is attacked over the network.
Am I affected by CVE-2026-73409?: Check whether you run @budibase/server (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.

Technical details

The vulnerability is an information disclosure (CWE-209) in packages/server/src/integrations/mongodb.ts. The MongoDB integration passes user-controlled tlsCertificateKeyFile and tlsCAFile configuration fields directly to the MongoDB driver as filesystem paths without validation, filtering, or directory confinement. When a datasource is verified via /api/datasources/verify, the MongoDB driver performs a real filesystem read of the attacker-supplied path. Files that exist but are not valid PEM return a "PEM routines" error; non-existent files return "ENOENT" with the path reflected. This creates a filesystem existence/read oracle. The attack requires authentication as a builder (local attack vector with user interaction to create/verify a datasource). Patches are available in version 3.40.0 and later, implementing PEM-from-content and path restrictions.

Affected products

Budibase Budibase <3.40.0

Identifiers

CVE-2026-73409
GHSA-ppr4-5f46-j9c6

Timeline

2026-07-24: disclosed
2026-07-24: patched: Fixed in version 3.40.0

References

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