# CVE-2026-119759: TrailBase 0.28.2 < 0.35.10 IDOR via Record API File Column


- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 9 Nov 2026
- **Updated:** 12 Nov 2026
- **Also known as:** GHSA-cr83-43p9-27qg

## What is CVE-2026-119759?

CVE-2026-119759 is a high-severity vulnerability in trailbaseio trailbase, published on 9 Nov 2026. 

### Official description

TrailBase 0.28.2 before 0.35.10 contains an insecure direct object reference in std.FileUpload columns, where the Record API accepts attacker-supplied object-store file ids on insert and update without ownership validation. An authenticated attacker who can read a victim’s row can recover its stripped file id via a $like filter and then permanently delete or orphan the victim’s file by deleting or nulling a record they own.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-119759 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-119759 is a high-severity vulnerability in trailbaseio trailbase, published on 9 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-119759 in the wild and no public exploit code.

Affected product: trailbaseio trailbase. 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-119759/ (Markdown: https://insights.sbomify.com/CVE-2026-119759/index.md)
```

## Sources

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

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