Service interruption via deterministic cache-key hash collisions
Published Jun 5, 2026 · Updated Jun 5, 2026
Algorithmic complexity in ByteDance InfiniStore 0.2.33 and earlier allows local users to interrupt service via colliding cache keys. The process-wide kv_map uses deterministic std::hashstd::string bucket placement for attacker-influenced keys, so collisions reduce map operations from O(1) to O(n). Exploitation requires low privileges and a collision set matched to the host C++ library; the resulting work blocks the single-threaded libuv path and causes timeouts.
Summary
What happened
Algorithmic complexity in ByteDance InfiniStore 0.2.33 and earlier allows local users to interrupt service via colliding cache keys. The process-wide kv_map uses deterministic std::hashstd::string bucket placement for attacker-influenced keys, so collisions reduce map operations from O(1) to O(n). Exploitation requires low privileges and a collision set matched to the host C++ library; the resulting work blocks the single-threaded libuv path and causes timeouts.
The record
- CVE
- CVE-2026-11312
- Published
- Jun 5, 2026
- Updated
- Jun 5, 2026
- Vendor
- ByteDance
- Product
- InfiniStore
- Classifications
- CWE-404, CWE-407, T1499.003
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 5, 2026CVE publishedPublication date reported by the CVE source.
- Jun 5, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.2.0
- Affected versionversion=0.2.1
- Affected versionversion=0.2.10
- Affected versionversion=0.2.11
- Affected versionversion=0.2.12
- Affected versionversion=0.2.13
- Affected versionversion=0.2.14
- Affected versionversion=0.2.15
- Affected versionversion=0.2.16
- Affected versionversion=0.2.17
- Affected versionversion=0.2.18
- Affected versionversion=0.2.19
- Affected versionversion=0.2.2
- Affected versionversion=0.2.20
- Affected versionversion=0.2.21
- Affected versionversion=0.2.22
- Affected versionversion=0.2.23
- Affected versionversion=0.2.24
- Affected versionversion=0.2.25
- Affected versionversion=0.2.26
- Affected versionversion=0.2.27
- Affected versionversion=0.2.28
- Affected versionversion=0.2.29
- Affected versionversion=0.2.3
- Affected versionversion=0.2.30
- Affected versionversion=0.2.31
- Affected versionversion=0.2.32
- Affected versionversion=0.2.33
- Affected versionversion=0.2.4
- Affected versionversion=0.2.5
- Affected versionversion=0.2.6
- Affected versionversion=0.2.7
- Affected versionversion=0.2.8
- Affected versionversion=0.2.9
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- InfiniStore hash-flood proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo