Cyber Resilience

CVE-2023-2976

Google Guava ≤ 32.0.0

Published
14 June 2023
Modified
25 February 2026
Patch / advisory
CVSS Score v3.1 5.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
EPSS Score 0.0025 16th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2023-2976 is a medium-severity Files or Directories Accessible to External Parties (CWE-552) vulnerability in Google Guava. Its CVSS base score is 5.5 (Medium).

Operationally, ranked at the 16th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

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…

more

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.

CWE(s)

Related Threats

CVEs Like This One

CVE-2025-1916Same vendor: Google
CVE-2024-11116Same vendor: Google
CVE-2023-35693Same vendor: Google
CVE-2025-12435Same vendor: Google
CVE-2026-8538Same vendor: Google
CVE-2026-0157Same vendor: Google
CVE-2026-13928Same vendor: Google
CVE-2023-21162Same vendor: Google
CVE-2024-3168Same vendor: Google
CVE-2026-11097Same vendor: Google

Affected Assets

google
guava
≤ 32.0.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)
  • 5 hardening rules · 2 OS baselines
Validate
Prove the fix (OWASP ASVS)
  • V8.4.2

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

addresses: CWE-552

Controls on authorized publication limit files and directories with nonpublic data from becoming accessible to external parties.

addresses: CWE-552

Controlling and documenting P2P file sharing prevents files and directories from being made accessible to external parties for unauthorized distribution.

addresses: CWE-552

Identifying and documenting file and directory locations allows restriction of access to external parties.

addresses: CWE-552

Protecting backup files ensures they are not accessible to external parties or unauthorized spheres.

addresses: CWE-552

Sanitizing equipment before off-site maintenance reduces the risk of files or directories containing sensitive data becoming accessible to external parties.

addresses: CWE-552

Policy restricts media access to authorized parties only, preventing exposure of resources to external or unauthorized actors.

addresses: CWE-552

Media access restrictions prevent files or directories from being accessible to external parties.

addresses: CWE-552

Employing and evaluating controls at documented alternate sites makes files and directories less likely to be accessible to external parties through physical or environmental weaknesses.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.AA-05 mostly match
prevents

Enforcing least-privilege permissions and authorization policies directly prevents unauthorized file/directory exposure.

PR.IR-01 mostly match
prevents

Logical segmentation and access protections stop external parties from reaching files that should remain internal.

PR.DS-01 partial match
prevents

Data-at-rest protections such as encryption or ACLs reduce the impact of unintended file exposure.

PR.PS-01 partial match
prevents

Hardened configuration baselines commonly include file-system permission settings that limit external access.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

mitigates

By tracing and retrieving all copies of information stored on endpoint and portable devices, the control reduces the likelihood that files remain accessible outside the organization’s security perimeter.

mitigates

Labeling information according to its sensitivity and specifying corresponding protection measures makes it less probable that files or directories containing sensitive content will be left accessible to external parties.

mitigates

Including asset location and ownership in the inventory, combined with secure disposal procedures, decreases the chance that files or directories remain accessible to external parties after they should have been removed or restricted.

mitigates

Solid perimeters and locked external access points stop files, devices, or directories containing sensitive data from being reachable by external parties who could otherwise walk in or break in.

mitigates

Authorizing and logging the removal of storage media, disabling unused ports, and monitoring transfers limit the exposure of files or directories to external parties outside the organization’s controlled environment.

mitigates

Segregating delivery/loading zones and controlling external doors prevents external parties from reaching directories or resources that should remain inaccessible.

References