# CVE-2026-31816: Budibase - Authentication Bypass

> Live exploitation tracking for CVE-2026-31816 by the CrowdSec Live Exploit Tracker, built from real-world attack data crowdsourced from CrowdSec's global network.

Page: https://tracker.crowdsec.net/cves/CVE-2026-31816

## Key facts

- **Exploitation phase:** Limited Exploitation. The vulnerability is known but shows very limited attacker interest or exploitation activity.
- **CVSS score:** 9.1
- **Public exploit available:** Yes
- **Affected products:** Budibase
- **Weaknesses:** CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection'))
- **Tags:** web_application

## Description

Budibase is a low code platform for creating internal tools, workflows, and admin panels. In 3.31.4 and earlier, the Budibase server's authorized() middleware that protects every server-side API endpoint can be completely bypassed by appending a webhook path pattern to the query string of any request. The isWebhookEndpoint() function uses an unanchored regex that tests against ctx.request.url, which in Koa includes the full URL with query parameters. When the regex matches, the authorized() middleware immediately calls return next(), skipping all authentication, authorization, role checks, and CSRF protection. This means a completely unauthenticated, remote attacker can access any server-side API endpoint by simply appending ?/webhooks/trigger (or any webhook pattern variant) to the URL.

## CrowdSec analysis

[CVE-2026-31816](https://euvd.enisa.europa.eu/vulnerability/CVE-2026-31816) is a critical vulnerability in Budibase versions 3.31.4 and earlier that allows unauthenticated remote attackers to bypass all authentication and authorization checks by manipulating the query string with a webhook path pattern. This flaw enables attackers to access any server-side API endpoint without credentials, potentially exposing sensitive data and administrative functions to exploitation. The vulnerability stems from improper regex handling in the authorization middleware, making it a significant risk for organizations using affected Budibase versions.

CrowdSec has been tracking this vulnerability and its exploits since 1st of April 2026.

CrowdSec has not observed any significant exploitation activity targeting CVE-2026-31816 across its network. As a result, no community-driven trend analysis is available for this vulnerability at this time.

Attackers exploit this vulnerability by sending crafted requests to any Budibase API endpoint, such as `/api/ta_users/search`, with a query string containing `/webhooks/trigger`, allowing unauthenticated access and bypassing authentication controls.

## Timeline

- 2026-03-09: CVE Published. CVE-2026-31816 is published to NVD.
- 2026-04-01: Rule Released. CrowdSec releases a rule to detect CVE-2026-31816 exploitation attempts against the CrowdSec Network.
- 2026-07-15: CrowdSec First Seen. CrowdSec observes in-the-wild exploitation of CVE-2026-31816 for the first time.

## References

- https://github.com/Budibase/budibase/security/advisories/GHSA-gw94-hprh-4wj8
- https://github.com/projectdiscovery/nuclei-templates/blob/main/http/cves/2026/CVE-2026-31816.yaml

## Live exploitation data

The [Live Exploit Tracker page](https://tracker.crowdsec.net/cves/CVE-2026-31816) follows observed exploitation activity for CVE-2026-31816. [Request an API key](https://tracker.crowdsec.net/request-api-key) for full access to its exploitation timeline, attacking IP addresses and blocklists.