Local file disclosure via insecure temporary creation
Published Jun 14, 2023 · Updated Feb 25, 2026
Insecure temporary-file creation in Google Guava 1.0 through 31.1 allows local users to read FileBackedOutputStream data. When buffered data exceeds the configured threshold, FileBackedOutputStream creates a file in Java's shared default temporary directory without restricting access to its owner. Exploitation requires access to that directory on Unix systems or app access on Android Ice Cream Sandwich, and the demonstrated consequence is disclosure of temporary file contents.
Summary
What happened
Insecure temporary-file creation in Google Guava 1.0 through 31.1 allows local users to read FileBackedOutputStream data. When buffered data exceeds the configured threshold, FileBackedOutputStream creates a file in Java's shared default temporary directory without restricting access to its owner. Exploitation requires access to that directory on Unix systems or app access on Android Ice Cream Sandwich, and the demonstrated consequence is disclosure of temporary file contents.
The record
- CVE
- CVE-2023-2976
- Published
- Jun 14, 2023
- Updated
- Feb 25, 2026
- Vendor
- Product
- Guava
- Classifications
- CWE-379, CWE-552, T1005
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 14, 2023CVE publishedPublication date reported by the CVE source.
- Feb 25, 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 <32.0.0
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
No public exploit references are available in this record.
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