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

Published Oct 22, 2026
·
Updated

CloudPirates Open Source Helm Charts is a collection of Helm charts. Prior to commit 271d415, pullrequesttarget workflow is vulnerable to cache poisoning and OIDC token theft. A pullrequesttarget workflow checks out fork code using github.event.pullrequest.head.sha or .head.ref. This gives attacker-controlled code access to base repository secrets and tokens. A pullrequesttarget 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.

Affected Software

1 affected component
CloudPirates Open Source Helm Charts

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade CloudPirates Open Source Helm Charts to a version that resolves this vulnerability.

    Patch 271d415

Event History

Oct 22, 2026
CVE Published
via MITRE·05:16 PM
Data Sourced
via MITRE·05:16 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who can exploit this issue?

An attacker who can submit a pull request from a fork can supply code that is checked out by the pull_request_target workflow. Exploitation also requires a workflow run in which that attacker-controlled code can access the base repository's secrets or tokens.

2

What is the potential impact beyond the pull request workflow?

The vulnerable workflow can write attacker-controlled content to a shared GitHub Actions cache. If a later release or publish workflow restores content from that cache scope, the poisoned cache entry can execute during that workflow.

3

Which versions or configurations are affected?

The issue affects the repository state before commit 271d415. The vulnerable condition is a pull_request_target workflow that checks out fork code using github.event.pull_request.head.sha or github.event.pull_request.head.ref and shares an Actions cache scope with release or publish workflows.

4

How can I determine whether remediation is present?

Verify that the repository includes commit 271d415. Also review pull_request_target workflows for checkouts of pull-request head SHA or head ref and confirm they cannot write to caches restored by release or publish workflows.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203