CVE-2026-40313 MervinPraison CVE debrief

Who should care

DevOps teams, security personnel, and developers using PraisonAI versions 4.5.139 and below should assess exposure and prioritize remediation due to the critical nature of this vulnerability and potential for supply chain compromise.

Why it matters

CVE-2026-40313 is a critical vulnerability in PraisonAI that allows for credential leakage via ArtiPACKED attacks. DevOps teams, security personnel, and developers should assess exposure and prioritize remediation due to the potential for supply chain compromise.

• Potential for malicious code injection
• Risk of repository secret exposure
• Compromise of downstream users
• Need for verification of affected versions and remediation

Technical summary

The vulnerability in PraisonAI, CVE-2026-40313, is caused by the use of actions/checkout without setting persist-credentials: false in GitHub Actions workflows. This leads to potential credential leakage via ArtiPACKED attacks, allowing an attacker to push malicious code, poison releases, steal repository secrets, and compromise downstream users. The issue affects PraisonAI versions 4.5.139 and below, and has been fixed in version 4.5.140. DevOps teams, security personnel, and developers should assess exposure and prioritize remediation due to the critical nature of this vulnerability and potential for supply chain compromise.

Defensive priority

High priority for remediation due to critical CVSS score of 9.1 and potential for supply chain compromise.

Recommended defensive actions

• Immediately upgrade to version 4.5.140 or later
• Review and update GitHub Actions workflows to set persist-credentials: false
• Monitor for and restrict the use of leaked tokens
• Conduct thorough inventory checks for affected versions
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The vulnerability is caused by the default behavior of actions/checkout in GitHub Actions workflows, which can lead to the leakage of GITHUB_TOKEN and ACTIONS_RUNTIME_TOKEN. This issue has been fixed in version 4.5.140.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.