CVE intelligence and bounded remediation

CVE-2025-36852 — A critical security vulnerability exists in remote cache extensions for common build systems utilizing bucket-based remote cache (such...

Critical CVSS 9.4

A critical security vulnerability exists in remote cache extensions for common build systems utilizing bucket-based remote cache (such as those using Amazon S3, Google Cloud Storage, or similar object storage) that allows any contributor with pull request privileges to inject compromised artifacts from an untrusted environment into trusted production environments without detection. The vulnerability exploits a fundamental design flaw in the "first-to-cache wins" principle, where artifacts built in untrusted environments (feature branches, pull requests) can poison the cache used by trusted environments (protected branches, production deployments). This attack bypasses all traditional security measures including encryption, access controls, and checksum validation because the poisoning occurs during the artifact construction phase, before any security measures are applied.

Severity
Critical
CVSS
9.4 (4.0)
Published
2025-06-10
CISA KEV
Not currently listed
Ecosystem
software/application
Weaknesses
CWE-829

Affected products

No browser-safe affected-product rows are available.

Matched remediation archetype

Supply-chain, dependency, build, and update integrity

This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.

Check exposure

  • Trace affected packages, source archives, build actions, plugins, installers, and updates from declared source to deployed artifact.
  • Confirm provenance, signatures or digests, namespace ownership, lockfile resolution, registry configuration, and build-runner trust boundaries.
  • Inventory direct, transitive, vendored, generated, and bundled copies across releases and distribution channels.

Remediate safely

  • Move to a maintained trusted artifact or remove the dependency; pin immutable identities and verify provenance and integrity before use.
  • Regenerate lockfiles and artifacts in a clean isolated build, minimize build credentials and network access, and produce an updated software bill of materials.
  • Require reviewed update policy, protected publishing, and reproducible or independently attestable builds where supported.

Authoritative sources

Complete CVE record and remediation plan

The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.