Security readout for executives and security teams
Plain-English summary
Budibase versions before 3.40.1 can expose stored REST datasource credentials through certain public queries. An unauthenticated attacker may redirect a request to infrastructure they control, potentially capturing bearer tokens, basic-auth credentials, or static authentication headers. Stolen credentials could expose connected business systems and data.
Executive priority
Treat as an urgent remediation for internet-accessible or publicly queried Budibase deployments. Upgrade promptly, identify exposed integrations, and rotate affected secrets. Compromise is not confirmed by vulnerability presence alone, but credential theft could extend impact into connected business systems.
Technical view
RestIntegration._req added datasource authentication and default headers without ensuring the final destination matched the configured datasource origin. Where a PUBLIC POST query accepts an absolute or parameterized path, an unauthenticated caller can redirect the authenticated request cross-origin. Budibase fixed the issue in 3.40.1. It is described as a bypass of CVE-2026-48152.
Likely exposure
Exposure requires Budibase below 3.40.1 and a public REST query whose destination can be influenced through an absolute or parameterized path. Risk is highest where such datasources store privileged credentials. The supplied evidence does not establish how commonly these conditions occur.
Exploitation context
The attack is remote, unauthenticated, and requires a vulnerable public-query configuration. Successful abuse can disclose reusable credentials to an attacker-controlled host. The supplied bundle marks this CVE as absent from KEV and provides no evidence of active exploitation.
Researcher notes
The central control failure was applying authentication headers before validating the final request origin. Assessment should focus on public query reachability, path controllability, credential-bearing headers, and unexpected outbound destinations. The record associates CWE-22, although the described security consequence is cross-origin credential disclosure. No public exploitation evidence is supplied.
Mitigation direction
- Upgrade Budibase to version 3.40.1 or later.
- Identify public REST queries with caller-influenced paths and restrict access until upgraded.
- Rotate credentials stored in potentially exposed REST datasources.
- Review connected systems and vendor guidance for additional response recommendations.
Validation and detection
- Confirm every Budibase deployment reports version 3.40.1 or later.
- Inventory PUBLIC POST queries and identify those using REST datasources.
- Review query configuration for absolute or parameterized caller-controlled paths.
- Check outbound and datasource logs for unexpected destination hosts.
- Verify potentially exposed datasource credentials were rotated and old credentials revoked.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-73407 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:H/SA:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:H/SA:N——GitHub_MVulnerability scoring details
Base CVSS 4.0 score
9CriticalVector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:H/SA:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/Budibase/budibase/security/advisories/GHSA-mqhr-6j6h-74p5CVE reference, GitHub_M · x_refsource_CONFIRM
- https://github.com/Budibase/budibase/pull/19239CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/Budibase/budibase/commit/8b1bca71501b11c68310351ef4f2c3028b2d5f08CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/Budibase/budibase/releases/tag/3.40.1CVE reference, GitHub_M · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.