Cache poisoning via predictable or incomplete hashing
Published Jun 4, 2026 · Updated Jun 4, 2026
Cache-key collisions in Streamlit before 1.53.1 allow local users to poison cached results with crafted data or P-mode images. The _to_bytes() method uses fixed seeds when sampling large Pandas, Polars, and NumPy inputs and omits palette bytes when hashing PIL P-mode images, so distinct inputs receive the same key. Exploitation requires low-privileged local access and precise control of unsampled values or image palettes; a successful collision returns stale or attacker-chosen data from shared caches.
Summary
What happened
Cache-key collisions in Streamlit before 1.53.1 allow local users to poison cached results with crafted data or P-mode images. The _to_bytes() method uses fixed seeds when sampling large Pandas, Polars, and NumPy inputs and omits palette bytes when hashing PIL P-mode images, so distinct inputs receive the same key. Exploitation requires low-privileged local access and precise control of unsampled values or image palettes; a successful collision returns stale or attacker-chosen data from shared caches.
The record
- CVE
- CVE-2026-10804
- Published
- Jun 4, 2026
- Updated
- Jun 4, 2026
- Vendor
- Snowflake
- Product
- Streamlit
- Classifications
- CWE-327, CWE-328, T1565.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 4, 2026CVE publishedPublication date reported by the CVE source.
- Jun 4, 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=1.0
- Affected versionversion=1.1
- Affected versionversion=1.10
- Affected versionversion=1.11
- Affected versionversion=1.12
- Affected versionversion=1.13
- Affected versionversion=1.14
- Affected versionversion=1.15
- Affected versionversion=1.16
- Affected versionversion=1.17
- Affected versionversion=1.18
- Affected versionversion=1.19
- Affected versionversion=1.2
- Affected versionversion=1.20
- Affected versionversion=1.21
- Affected versionversion=1.22
- Affected versionversion=1.23
- Affected versionversion=1.24
- Affected versionversion=1.25
- Affected versionversion=1.26
- Affected versionversion=1.27
- Affected versionversion=1.28
- Affected versionversion=1.29
- Affected versionversion=1.3
- Affected versionversion=1.30
- Affected versionversion=1.31
- Affected versionversion=1.32
- Affected versionversion=1.33
- Affected versionversion=1.34
- Affected versionversion=1.35
- Affected versionversion=1.36
- Affected versionversion=1.37
- Affected versionversion=1.38
- Affected versionversion=1.39
- Affected versionversion=1.4
- Affected versionversion=1.40
- Affected versionversion=1.41
- Affected versionversion=1.42
- Affected versionversion=1.43
- Affected versionversion=1.44
- Affected versionversion=1.45
- Affected versionversion=1.46
- Affected versionversion=1.47
- Affected versionversion=1.48
- Affected versionversion=1.49
- Affected versionversion=1.5
- Affected versionversion=1.50
- Affected versionversion=1.51
- Affected versionversion=1.52
- Affected versionversion=1.53.0
- Affected versionversion=1.6
- Affected versionversion=1.7
- Affected versionversion=1.8
- Affected versionversion=1.9
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- Streamlit cache-key collision reproductionsproof 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