dbcve.org
PraisonaiApplication · Praison

CVE-2026-40313

CRITICAL · 9.1 CVSS v3.1 Published 2026-04-14
Fix available
A fix is available. Upgrade to 4.5.140 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
PraisonAI is a multi-agent teams system. In versions 4.5.139 and below, the GitHub Actions workflows are vulnerable to ArtiPACKED attack, a known credential leakage vector caused by using actions/checkout without setting persist-credentials: false. By default, actions/checkout writes the GITHUB_TOKEN (and sometimes ACTIONS_RUNTIME_TOKEN) into the .git/config file for persistence, and if any subsequent workflow step uploads artifacts (build outputs, logs, test results, etc.), these tokens can be inadvertently included. Since PraisonAI is a public repository, any user with read access can download these artifacts and extract the leaked tokens, potentially enabling an attacker to push malicious code, poison releases and PyPI/Docker packages, steal repository secrets, and execute a full supply chain compromise affecting all downstream users. The issue spans numerous workflow and action files across .github/workflows/ and .github/actions/. This issue has been fixed in version 4.5.140.

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

PraisonAI versions 4.5.139 and below contain a supply-chain vulnerability in GitHub Actions workflows where actions/checkout writes the GITHUB_TOKEN to .git/config by default. When subsequent workflow steps upload artifacts, these tokens are inadvertently included, enabling anyone with read access to a public repository to extract tokens and perform supply-chain attacks.

MitigationUpdate to version 4.5.140 or add `persist-credentials: false` to all actions/checkout steps in .github/workflows/ and .github/actions/ directories.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
PraisonaiApplication
Affected:< 4.5.140

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
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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. Check installed PraisonAI version
    Run `pip show praisonai` or check your dependency lock file for the installed version number
    Affected if Version is 4.5.139 or below (< 4.5.140)
  2. Locate GitHub Actions workflow files
    Search for .github/workflows/*.yml or .yaml files in your repository
    Affected if Workflow files exist in .github/workflows/ or .github/actions/ directories
  3. Inspect actions/checkout usage
    Open each workflow file and search for 'actions/checkout' in steps
    Affected if Any workflow uses actions/checkout without specifying persist-credentials
  4. Verify persist-credentials setting
    For each actions/checkout action, check if `persist-credentials: false` is present in the with: section
    Affected if actions/checkout is used without `persist-credentials: false` (defaults to true, exposing token)
  5. Check for artifact upload steps
    Look for actions that upload artifacts (actions/upload-artifact, actions/upload-release-asset, etc.) in workflows using checkout
    Affected if Artifact upload steps exist in workflows that use unchecked-out actions - tokens in .git/config could be captured

You are affected if running PraisonAI below version 4.5.140 AND your repository contains GitHub Actions workflows using actions/checkout without the `persist-credentials: false` setting.

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
Upgrade available Upgrade to 4.5.140 or later
Fixed in 4.5.140
Interim mitigation

Update to version 4.5.140 or add `persist-credentials: false` to all actions/checkout steps in .github/workflows/ and .github/actions/ directories.

Recommended fix High confidence

4.5.140

  1. Upgrade PraisonAI to version 4.5.140 or later by updating your installation (e.g., pip install praisonai==4.5.140 or your package manager's equivalent upgrade command)
  2. Verify the upgrade was successful by checking the installed version
  3. If using the GitHub Actions workflows, ensure they are updated to use the fixed version of PraisonAI actions

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

Fix this in Praisonai Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-40313 — 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-40313 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