CVE-2026-68510: contain-rs bit-vec · Improper Input Validation
Affects contain-rs bit-vecSource CVE Database V5
Not known to be exploited · CVSS 6.9 Medium : upgrade to 0.10.0 when convenient.
Data as of 14 Nov 2026, 20:58 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 4.0 | 6.9 |
|---|
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 18% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.10.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 13 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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), the Metasploit, Exploit-DB and nuclei-templates index as of 14 Nov 2026.
What to do
Upgrade bit-vec and contain-rs/bit-vec to 0.10.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| contain-rsbit-vec | Affected
| Fixed in
|
crates.iocontain-rs/bit-vecpkg:cargo/contain-rs/bit-vecOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade to bit-vec version 0.10.0 or later, where this vulnerability has been fixed. No other mitigation is required as the issue is resolved in the official patch.
Description
CVE-2026-68510 affects the contain-rs bit-vec library prior to version 0.10.0. The vulnerability involves improper input validation leading to undefined behavior when deserializing BitVec data from untrusted sources and subsequently using unsafe get_unchecked operations. This can cause incorrect behavior in applications using the affected versions. The issue is fixed in version 0.10.0.