TrailBase 0.28.2 < 0.35.10 IDOR via Record API File Column
TrailBase 0.28.2 before 0.35.10 is affected only when Record API tables have std.FileUpload columns. The fix is in 0.35.10.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 0.35.10
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. TrailBase version 0.28.2 up to but not including 0.35.10 Record API tables with std.FileUpload columns
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 17/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
TrailBase, a backend platform with a Record API, is affected by an insecure direct object reference flaw in its file-upload columns. A logged-in attacker over the network can point a record they own at another user's or table's stored file, letting them read that file's contents or permanently delete it.
Read the original description
TrailBase 0.28.2 before 0.35.10 contains an insecure direct object reference vulnerability that allows authenticated attackers to manipulate the object-store id metadata within std.FileUpload columns without ownership validation during insert and update operations. Attackers can reference another user's or table's file id in a record they own to read the victim's file bytes through their own record, or trigger permanent deletion of the victim's file by deleting or nulling their own record, while also using a $like filter on the file column to brute-force recover stripped ids character by character.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.6/10CVSS 8.6
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 24 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
TrailBase version 0.28.2 up to but not including 0.35.10 Record API tables with std.FileUpload columnsUpgrade to a fixed version: 0.35.10.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- trailbaseio trailbase
From 0.28.2 · fixed in 0.35.10
Evidence 2
- Patch
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-119759
Is CVE-2026-119759 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The Record API does not properly check object ownership for file columns, so a user can change the object-store id metadata in their own record to read another user's or table's file bytes. The same weakness can be used to permanently delete a victim's file and to recover stripped file ids with a $like filter.Source: vulncheck.com
Which versions are affected by CVE-2026-119759?
trailbase: from 0.28.2 before 0.35.10.Source: cve.now feed data
Am I affected, and how do I check?
TrailBase versions from 0.28.2 up to but not including 0.35.10 are affected, and only where Record API tables have std.FileUpload columns. To check, look at the installed TrailBase version and at whether any table schema uses std.FileUpload columns.Source: vulncheck.com
How do I fix CVE-2026-119759?
Upgrade TrailBase to 0.35.10 or later, which contains the fix. The advisory facts do not list a workaround.Source: vulncheck.com