Local privilege escalation via temporary-library replacement race
Published Feb 25, 2025 · Updated Feb 25, 2025
Local privilege escalation in Gradle Build Tool 8.12 allows local users to execute code with a build user's privileges via a file race. A default native-platform initialization path copies native binaries into the shared system temporary directory, where another user can rapidly delete and replace them before loading. Exposure requires a Unix-like host whose temporary directory lacks sticky-bit protection and is executable; Windows and modern macOS are unaffected.
Summary
What happened
Local privilege escalation in Gradle Build Tool 8.12 allows local users to execute code with a build user's privileges via a file race. A default native-platform initialization path copies native binaries into the shared system temporary directory, where another user can rapidly delete and replace them before loading. Exposure requires a Unix-like host whose temporary directory lacks sticky-bit protection and is executable; Windows and modern macOS are unaffected.
The record
- CVE
- CVE-2025-27148
- Published
- Feb 25, 2025
- Updated
- Feb 25, 2025
- Vendor
- Gradle, Inc.
- Product
- Gradle Build Tool
- Classifications
- CWE-378, CWE-379, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 25, 2025CVE publishedPublication date reported by the CVE source.
- Feb 25, 2025Record 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== 8.12
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