# CVE-2026-54532: CloudPirates Open Source Helm Charts: pull_request_target workflow vulnerable to cache poisoning and OIDC token theft


- **Severity:** Medium 6.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:N/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 22 Oct 2026
- **Updated:** 22 Oct 2026
- **Also known as:** GHSA-gv8x-4mc5-r65r

## What is CVE-2026-54532?

CVE-2026-54532 is a medium-severity vulnerability in CloudPirates-io helm-charts, published on 22 Oct 2026. 

### Official description

CloudPirates Open Source Helm Charts is a collection of Helm charts. Prior to commit 271d415, pull_request_target workflow is vulnerable to cache poisoning and OIDC token theft. A pull_request_target workflow checks out fork code using github.event.pull_request.head.sha or .head.ref. This gives attacker-controlled code access to base repository secrets and tokens. A pull_request_target workflow writes to a shared Actions cache. A subsequent release or publish workflow restores from the same cache scope, allowing a poisoned cache entry to execute during release. This issue has been patched via commit 271d415.

Weakness: CWE-829 (Inclusion of Functionality from Untrusted Control Sphere)

## Which versions are affected by CVE-2026-54532?


## How do I fix CVE-2026-54532?

No fix has been published for CVE-2026-54532 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-54532 being exploited?

There is no known exploitation of CVE-2026-54532 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-54532 and fix it if it is affected.

What it is: CVE-2026-54532 is a medium-severity vulnerability in CloudPirates-io helm-charts, published on 22 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-54532 in the wild and no public exploit code.

Affected product: CloudPirates-io helm-charts. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-54532/ (Markdown: https://insights.sbomify.com/CVE-2026-54532/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-54532
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-54532
- OSV: https://osv.dev/vulnerability/CVE-2026-54532

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-54532/
Summaries are generated and may contain mistakes; the official description above is the record.