Information Disclosure in Guava

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

3.3 · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

EPSS

• CVE-2020-8908: 0.92% estimated exploitation activity in the next 30 days; percentile 60.45 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

A temp directory creation vulnerability exists in Guava prior to version 32.0.0 allowing an attacker with access to the machine to potentially access data in a temporary directory created by the Guava com.google.common.io.Files.createTempDir(). The permissions granted to the directory created default to the standard unix-like /tmp ones, leaving the files open. Maintainers recommend explicitly changing the permissions after the creation of the directory, or removing uses of the vulnerable method.

Published by the source

25 Mar 2021, 17:04 UTC

Last modified by the source

23 Feb 2026, 22:45 UTC

Source last checked

26 Oct 2026, 16:44 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-5mg8-w23w-74h3

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2020-8908

Advisory: Information Disclosure in Guava
IDs: CVE-2020-8908, GHSA-5mg8-w23w-74h3
Record: https://patchnext.com/advisories/cve-2020-8908 (revision 1, source checked 26 Oct 2026, 16:44 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 3.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: com.google.guava:guava 32.0.0-android. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven com.google.guava:guava: affected < 32.0.0-android; fixed in 32.0.0-android

## Suggested inspection (read-only)
- Maven com.google.guava:guava: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on com.google.guava:guava.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-5mg8-w23w-74h3 (GitHub-reviewed advisory GHSA-5mg8-w23w-74h3 lists affected ranges: Maven com.google.guava:guava >=0 <32.0.0-android)

Commands are suggestions: review each one before running it.