Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Network-reachable but requires low-privilege user to open a crafted file (PR:L, UI:R); impact is application-level availability only, no data exposure (C:N/I:N, A:L).
Primary rating from Vendor (vuldb).
CVSS VectorVendor: vuldb
Lifecycle Timeline
1DescriptionCVE.org
A vulnerability was detected in TrailDB 0.6. Impacted is the function tdb_open of the file /src/tdb.c of the component TOC Validation. The manipulation results in out-of-bounds read. It is possible to launch the attack remotely. The exploit is now public and may be used. The project was informed of the problem early through an issue report but has not responded yet.
AnalysisAI
Out-of-bounds read in TrailDB 0.6 allows a remote attacker with low privileges to crash an application processing a crafted TrailDB file. The vulnerable code path is the TOC (Table of Contents) validation logic inside tdb_open() in /src/tdb.c, triggered when a maliciously formed TrailDB file is opened. Publicly available exploit code exists (CVSS 4.0 E:P); no KEV listing and no patch - the project has not responded to the coordinated disclosure filed via GitHub issue #149.
Technical ContextAI
TrailDB is a compact, open-source binary format and C library for storing and querying append-only event streams, primarily used for analytics workloads. The tdb_open() function in /src/tdb.c is responsible for parsing the file header and TOC structure that maps internal data segments. CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) covers the root cause here: during TOC validation, attacker-controlled field values in the file header can cause the parser to read memory beyond the allocated buffer. Because the library is written in C with no bounds-safe abstractions, a malformed TOC entry can redirect a read pointer outside valid memory. The CVSS 4.0 vector confirms no confidentiality or integrity impact (VC:N/VI:N), consistent with a read-only memory safety bug that primarily risks a process crash rather than code execution.
RemediationAI
No vendor-released patch identified at time of analysis. The project was notified through GitHub issue #149 (https://github.com/traildb/traildb/issues/149) but has not responded, and no fixed release is available. The primary compensating control is to reject untrusted or externally sourced TrailDB files before passing them to tdb_open(), since the vulnerability is triggered at file-open time during TOC parsing - this eliminates the attack surface at the cost of restricting data ingestion from external parties. Applications that must process untrusted TrailDB files should sandbox the parsing process (e.g., run tdb_open in a subprocess with limited privileges and OS-level memory isolation such as seccomp) to contain a crash and prevent exploitation of any future escalation. Organizations should monitor the GitHub repository for any upstream patch and update promptly when one is released.
Same weakness CWE-119 – Buffer Overflow
View allSame technique Buffer Overflow
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-59991
GHSA-3r54-xjq4-jwjm