Artifact injection via shared cache namespace
Published Jun 10, 2025 · Updated Jun 10, 2025
Build cache poisoning in affected Nx remote-cache plugins allows remote authenticated users to inject artifacts into trusted builds. The plugins let pull-request and protected-branch jobs write the same cache key, and the first artifact stored becomes the trusted result. Pull-request privileges and a shared writable remote-cache namespace are required; a poisoned artifact can execute when a trusted build consumes it.
Summary
What happened
Build cache poisoning in affected Nx remote-cache plugins allows remote authenticated users to inject artifacts into trusted builds. The plugins let pull-request and protected-branch jobs write the same cache key, and the first artifact stored becomes the trusted result. Pull-request privileges and a shared writable remote-cache namespace are required; a poisoned artifact can execute when a trusted build consumes it.
The record
- CVE
- CVE-2025-36852
- Published
- Jun 10, 2025
- Updated
- Jun 10, 2025
- Vendor
- Niklas Portmann
- Product
- nx-remotecache-azure
- Classifications
- CWE-829, T1195.002
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 10, 2025CVE publishedPublication date reported by the CVE source.
- Jun 10, 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=0
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
- CREEP pull-request cache-poisoning procedureproof of concept · demonstrated
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