# CVE-2026-81335: Baserow before 2.3.1 Unauthenticated Data Disclosure via Discarded Permission Check on Builder Data Sources

> Unauthenticated attackers can access sensitive data from Builder data sources due to a missing permission check enforcement in Baserow.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Aug 2026
- **Updated:** 27 Aug 2026
- **Also known as:** GHSA-h84g-8x85-mw8v

## What is CVE-2026-81335?

CVE-2026-81335 is a high-severity missing authorization vulnerability in Baserow, published on 27 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Baserow dispatches an Application Builder data source without acting on the result of its permission check. The dispatch and record-name views in backend/src/baserow/contrib/builder/api/data_sources/views.py are declared with a permission class that admits any caller, so a request carrying no credential reaches the handler. DataSourceService.dispatch_data_sources in backend/src/baserow/contrib/builder/data_sources/service.py then calls check_multiple_permissions without asking it to raise, and neither stores nor examines the mapping of denials it returns, so a denied check leaves execution to continue and the data source is dispatched whatever the caller's identity. The dispatch runs with the integration's own credentials, so an unauthenticated request naming a data source receives the rows and fields that source reads. Identifiers are small integers and can be enumerated. Version 2.3.1 passes raise_exception to the same call.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-81335?


## How do I fix CVE-2026-81335?

No fix has been published for CVE-2026-81335 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-81335 being exploited?

There is no known exploitation of CVE-2026-81335 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-81335 and fix it if it is affected.

What it is: CVE-2026-81335 is a high-severity missing authorization vulnerability in Baserow, published on 27 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-81335 in the wild and no public exploit code.

Affected product: Baserow. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-81335/ (Markdown: https://insights.sbomify.com/CVE-2026-81335/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-81335
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-81335
- OSV: https://osv.dev/vulnerability/CVE-2026-81335

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-81335/
Summaries are generated and may contain mistakes; the official description above is the record.