Skip to content

fix(deps): update dependency com.google.guava:guava to v32 [security] - #42

Open
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/maven-com.google.guava-guava-vulnerability
Open

fix(deps): update dependency com.google.guava:guava to v32 [security]#42
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/maven-com.google.guava-guava-vulnerability

Conversation

@renovate

@renovaterenovateBot commented Apr 15, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

PackageChangeAgeConfidence
com.google.guava:guava31.1-jre32.0.0-androidageconfidence

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Guava vulnerable to insecure use of temporary directory

CVE-2023-2976 / GHSA-7g45-4rm6-3mm3

More information

Details

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, maintainers recommend using version 32.0.1 as version 32.0.0 breaks some functionality under Windows.

Severity

  • CVSS Score: 5.5 / 10 (Medium)
  • Vector String: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


Information Disclosure in Guava

CVE-2020-8908 / GHSA-5mg8-w23w-74h3

More information

Details

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.

Severity

  • CVSS Score: 3.3 / 10 (Low)
  • Vector String: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovaterenovateBot changed the title fix(deps): update dependency com.google.guava:guava to v32 [security]fix(deps): update dependency com.google.guava:guava to v32 [security] - autoclosedApr 27, 2026
@renovaterenovateBot closed this Apr 27, 2026
@renovate
renovateBot deleted the renovate/maven-com.google.guava-guava-vulnerability branch April 27, 2026 17:49
@renovaterenovateBot changed the title fix(deps): update dependency com.google.guava:guava to v32 [security] - autoclosedfix(deps): update dependency com.google.guava:guava to v32 [security]Apr 27, 2026
@renovaterenovateBot reopened this Apr 27, 2026
@renovate
renovateBotforce-pushed the renovate/maven-com.google.guava-guava-vulnerability branch 2 times, most recently from 1c70bca to bcfa94fCompareApril 27, 2026 21:25
@renovate
renovateBotforce-pushed the renovate/maven-com.google.guava-guava-vulnerability branch 2 times, most recently from d79fe13 to 0ec081fCompareMay 22, 2026 17:51
@renovate
renovateBotforce-pushed the renovate/maven-com.google.guava-guava-vulnerability branch from 0ec081f to 0bee67aCompareJuly 16, 2026 17:56
@renovate
renovateBotforce-pushed the renovate/maven-com.google.guava-guava-vulnerability branch from 0bee67a to 9f83a53CompareAugust 11, 2026 23:03
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants