CVE-2023-2976 is a medium-severity (CVSS 5.5) CWE-552 vulnerability in com.google.guava:guava. A fix is available for com.google.guava:guava — see the affected versions and patch details below.
Use of temporary directory for file creation in `FileBackedOutputStream` in Guava
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2023-2976.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
com.google.guava:guavaReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Use of Java's default temporary directory for file creation in FileBackedOutputStream in Google Guava versions 1.0 to 31.1 on Unix systems and Android Ice Cream Sandwich allows other users and apps on the machine with access to the default Java temporary directory to be able to access the files created by the class.
Even though the security vulnerability is fixed in version 32.0.0, we recommend using version 32.0.1 as version 32.0.0 breaks some functionality under Windows.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.google.guava:guava | ≥ 1.0&&< 32.0.0-android | 32.0.0-androidcom.google.guava:guava:32.0.0-android |
Affected Products
guavagoogleDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.google.guava:guava, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.google.guava:guava to 32.0.0-android or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-2976 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
Red Hat Single Sign-On 7 ships the affected component as a layered product of Red Hat JBoss Enterprise Application 7, and as such is affected by this flaw. However, Single Sign-On 7 does not use the affected code and is not vulnerable to exploit.
Temp files should be created with sufficiently non-predictable names and in a secure-permissioned, dedicated temp folder.Source: Red Hat security advisory for CVE-2023-2976 (CC BY 4.0)
| Product | Fixed in | Advisory |
|---|---|---|
| AMQ Broker 7.11.2 | guava | RHSA-2023:5491 |
| MTA-6.2-RHEL-8 | mta/mta-rhel8-operator:6.2.2-3 | RHSA-2024:1027 |
| OCP-Tools-4.12-RHEL-8 | jenkins-0:2.426.3.1706515686-3.el8 | RHSA-2024:0778 |
| OCP-Tools-4.14-RHEL-8 | jenkins-2-plugins-0:4.14.1706516441-1.el8 | RHSA-2024:0777 |
| Red Hat AMQ Streams 2.5.0 | see advisory | RHSA-2023:5165 |
| Red Hat AMQ Streams 2.6.0 | guava | RHSA-2023:7678 |
| Red Hat AMQ Streams 2.7.0 | see advisory | RHSA-2024:3527 |
| Red Hat build of Apache Camel 4.4.0 for Spring Boot | guava | RHSA-2024:2707 |
Frequently Asked Questions
Is CVE-2023-2976 in your dependencies?
Find it across Maven, including transitive dependencies.