CVE-2026-45132
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCloudPirates Open Source Helm Charts is a collection of Helm charts. Prior to commit fcf9302, a GitHub Actions workflow (generate-schema.yaml) exposes sensitive credentials (Personal Access Token and SSH signing key) to fork-controlled code due to unsafe checkout and credential handling practices. This issue has been patched via commit fcf9302.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe GitHub Actions workflow (generate-schema.yaml) in CloudPirates Open Source Helm Charts improperly handles credentials during repository checkout, exposing Personal Access Tokens and SSH signing keys to fork-controlled code. This occurs due to unsafe checkout and credential handling practices that allow potentially malicious forks to access these sensitive credentials.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate the generate-schema.yaml workflow fileCheck if .github/workflows/generate-schema.yaml exists in the repositoryAffected if the workflow file does not exist (not vulnerable to this specific issue)
-
Identify if workflow runs on pull request eventsExamine the workflow file for 'on: pull_request' or 'on: pull_request_target' triggers in the workflow configurationAffected if the workflow has a pull_request or pull_request_target trigger (vulnerable to fork-based attacks)
-
Verify credential usage in the workflowSearch the workflow file for ${{ secrets.* }} references, particularly for PERSONAL_ACCESS_TOKEN, SSH_SIGNING_KEY, or similar credential namesAffected if the workflow uses secrets (PAT, SSH keys) that could be exfiltrated
-
Examine checkout action security settingsLook for 'actions/checkout' steps and check if 'persist-credentials: false' is set, or if 'ref' is properly set to a safe referenceAffected if checkout uses persist-credentials: true or lacks proper ref configuration, allowing credentials to flow to fork code
-
Compare to patched commitCheck the git history for the repository or workflow file. Verify if the last update includes commit fcf9302 or later which contains the security fixAffected if the workflow predates commit fcf9302 or the fix has not been applied
The environment is affected if the generate-schema.yaml workflow runs on pull_request events from external forks while exposing secrets through an unsafe checkout configuration.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade to the patched version (commit fcf9302 or later) which implements safe checkout practices and proper credential handling to prevent credential exfiltration by untrusted forks.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-45132 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-45132 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data