OSV-2017-126
Bad-cast to const std::__1::__less<unsigned long, unsigned long> *_start
No scoreFix available
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=606
Crash type: Bad-cast
Crash state:
Bad-cast to const std::__1::__less<unsigned long, unsigned long> *_start
What each source reports
OSV No score
Bad-cast to const std::__1::__less<unsigned long, unsigned long> *_start
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=606
Crash type: Bad-cast
Crash state:
Bad-cast to const std::__1::__less<unsigned long, unsigned long> *_start
- Record
OSV-2017-126- Updated
- 2026-11-02
Affected packages
| Package | Affected | Fixed |
|---|---|---|
libtsmOSS-Fuzz |
Commit ranges | Not evaluated |
Not evaluated means the source gave git commits or a range we can't read, so we can't tell which releases are affected. A fixed version beside it is the source’s own claim.
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
OSV-2017-126 is a vulnerability with no CVSS score yet in libtsm, published January 15, 2021. No source lists public exploit code. A source reports a fix.