dbcve.org
Code InjectionWeakness · CWE-94

CVE-2026-45131

CRITICAL · 10.0 CVSS v3.1 Published 2026-06-01
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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 · unedited
CloudPirates Open Source Helm Charts is a collection of Helm charts. Prior to commit fcf9302, a GitHub Actions workflow (pull-request.yaml) executes attacker-controlled code from fork pull requests in a privileged context, exposing repository secrets including Docker Hub credentials and tokens without requiring maintainer approval. 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 confidence

A GitHub Actions workflow (pull-request.yaml) in CloudPirates Helm Charts executes attacker-controlled code from fork pull requests in a privileged context, allowing malicious actors to exfiltrate repository secrets including Docker Hub credentials and tokens without any maintainer approval.

MitigationApply the patch from commit fcf9302, which prevents execution of untrusted code from fork pull requests in privileged contexts.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate the pull-request.yaml workflow file
    Check if the file .github/workflows/pull-request.yaml exists in your repository. This file is the workflow referenced in the CVE.
    Affected if The file exists and is active in the repository.
  2. Verify the workflow trigger events
    Open .github/workflows/pull-request.yaml and examine the 'on:' section. Look for 'pull_request' or 'pull_request_target' event triggers.
    Affected if The workflow triggers on 'pull_request' or 'pull_request_target' events without additional approval requirements.
  3. Inspect GITHUB_TOKEN permissions
    In the workflow file, check the 'permissions:' block or the job-level permissions. Look for permissions such as 'contents: write', 'secrets: write', or broad write access.
    Affected if The workflow runs with elevated GITHUB_TOKEN permissions (write access to contents, secrets, or other sensitive scopes).
  4. Check for maintainer approval requirements
    Look for 'concurrency:' groups that cancel in-progress runs, or any 'required_reviews' or approval gate mechanisms on the pull request trigger.
    Affected if There is NO maintainer approval requirement or concurrency controls to gate untrusted pull request runs.
  5. Confirm secrets or Docker Hub credentials exist in the environment
    Review repository secrets and environment variables used in the workflow. Check if Docker Hub credentials, tokens, or other sensitive secrets are accessible to this workflow.
    Affected if The workflow has access to Docker Hub credentials, tokens, or other secrets that could be exfiltrated by an attacker.

You are affected if your repository contains an active .github/workflows/pull-request.yaml that triggers on pull_request or pull_request_target events, runs with elevated permissions, and has no maintainer approval requirement to gate untrusted fork code.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Apply the patch from commit fcf9302, which prevents execution of untrusted code from fork pull requests in privileged contexts.

Recommended fix Moderate confidence

Upgrade to a version/branch containing commit fcf9302 or later

  1. 1. Locate the pull-request.yaml workflow file in the repository at .github/workflows/pull-request.yaml
  2. 2. Review the current workflow configuration to identify security gaps (e.g., absence of workflow concurrency controls, missing trigger restrictions)
  3. 3. Examine the fix implemented in commit fcf9302 on the repository
  4. 4. Apply the security improvements from commit fcf9302 to the workflow file, ensuring that attacker-controlled code from fork pull requests is not executed in a privileged context
  5. 5. Remove or rotate any Docker Hub credentials and tokens that may have been exposed, as they should be considered compromised
  6. 6. Verify the updated workflow functions correctly before merging

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the patch applied

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-45131 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-45131 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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