CVE Intelligence
Medium

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

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.

Published Oct 22, 2026 · Updated Oct 23, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: GitHub_M

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.2% (30-day exploitation probability)+1
  • Technical severity (medium)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.19%
ahead of 8% of scored CVEs · Oct 27, 2026
Affects
CloudPirates-io
Helm-charts
CVSS base
6.9
Medium · 2 source(s)

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (CloudPirates-io Helm-charts).
  2. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  3. Exploitation requires user interaction: tighten email/web filtering and warn affected users.
  4. Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
CloudPirates-io Helm-charts version < 271d415975a64b7958d2740526dca870b70c8c21 Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
High
User interaction
Required
Scope
Changed
Confidentiality
None
Integrity
High
Availability
Low

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
6.9 CVSS 3.1 Medium 1.7 4.7 security-advisories@github.com via NIST National Vulnerability Database
6.9 CVSS 3.1 Medium — — GitHub_M via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:N/I:H/A:L (score shown at the top: security-advisories@github.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-829

Other CVEs with this weakness →

EPSS over time FIRST

Oct 23, 2026 → Oct 27, 2026 · 5 reading(s) · max 0.19%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
web/proxy/WAF logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first.

  • 2026
  • Source status changed · Received → Deferred
    Oct 23, 2026 · NIST National Vulnerability Database
  • Affected products added · cloudpirates-io/helm-charts
    Oct 22, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 22, 2026
  • CVSS changed · 6.9
    Oct 22, 2026 · NIST National Vulnerability Database
  • Source status changed · → Received
    Oct 22, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 22, 2026 · Alertas do Telegram
  • CVE published
    Oct 22, 2026 · GitHub_M

Source activity

Repeated readings are counted rather than listed.

  • 1× References added · Oct 22, 2026 – Oct 22, 2026
  • 1× Official description updated · Oct 22, 2026 – Oct 22, 2026

References

2 on the record

Elsewhere on this site

CloudPirates-io
every CVE for this vendor
CWE-829
other pages naming this weakness

Related CVEs (same products)

  • Critical CVE-2026-45132 CloudPirates Open Source Helm Charts: GitHub Actions workflow leaks PAT and SSH signing key via unsafe credential handling Jun 1, 2026
  • Critical CVE-2026-45131 CloudPirates Open Source Helm Charts: GitHub Actions pull_request_target workflow allows secret exfiltration via fork pull requests Jun 1, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No fixed version, patch or mitigation documented.
  • No CISA SSVC assessment.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-54532 is "CloudPirates Open Source Helm Charts: pull_request_target workflow vulnerable to cache poisoning and OIDC token theft", rated Medium. It affects Helm-charts (CloudPirates-io); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 6.9 describes technical severity. EPSS 0.19% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.