Skip to main content
VulnerabilityPublished Updated

CVE-2026-19955: TrailDB · Out-of-bounds Read

Affects TrailDBSource CVE Database V5

0
Compare

Public exploit available · CVSS 5.1 Medium.

Data as of 14 Nov 2026, 20:44 UTC

CVSS 4.0 base score
5.1Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 35% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    CVSS exploit maturity: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 14 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
TrailDBAffected
  • =0.6
Fixed in–
GitHubtraildb/traildbpkg:github/traildb/traildbOther threatsAffected
  • =0.6
Fixed in–

CPE configurations (1)

  • cpe:2.3:a:traildb:traildb:*:*:*:*:*:*:*:*

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Since the project has not responded or released a fix, users should monitor official sources for updates. Until a fix is available, consider restricting network access to the vulnerable service or applying other environment-specific mitigations to reduce exposure.

Description

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.

References

Community reviews

Loading reviews…