CVE-2026-40313: PraisonAI: ArtiPACKED Vulnerability via GitHub Actions Credential Persistence

Published Apr 14, 2026
·
Updated

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 GITHUBTOKEN (and sometimes ACTIONSRUNTIMETOKEN) 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.

Affected Software

2 affected components
PraisonAI praisonai<=4.5.139
Praison PraisonAI<4.5.140

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade actions/checkout to a version that resolves this vulnerability.

    Fixed in 4.5.140
  2. Configuration

    Update all uses of actions/checkout in .github/workflows/ and .github/actions/ to set persist-credentials: false so GITHUB_TOKEN (and sometimes ACTIONS_RUNTIME_TOKEN) are not written to .git/config for persistence.

    GitHub Actions workflows using actions/checkout persist-credentials = false

Event History

Apr 14, 2026
CVE Published
via MITRE·03:10 AM
Data Sourced
via MITRE·03:10 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·04:17 AM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-40313?

CVE-2026-40313 has been classified with a high severity due to its potential for credential leakage.

2

How do I fix CVE-2026-40313?

To fix CVE-2026-40313, update your PraisonAI installation to version 4.5.140 or later and ensure that actions/checkout is configured to prevent credential persistence.

3

What versions of PraisonAI are affected by CVE-2026-40313?

CVE-2026-40313 affects all versions of PraisonAI up to and including 4.5.139.

4

What type of attack does CVE-2026-40313 involve?

CVE-2026-40313 involves an ArtiPACKED attack which is a method for credential leakage via improperly configured GitHub Actions workflows.

5

What steps can I take to secure my GitHub Actions against CVE-2026-40313?

To secure your GitHub Actions against CVE-2026-40313, ensure that you configure actions/checkout to avoid persisting credentials and regularly update to the latest software versions.

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