VulnerabilityPublished 14 Apr 2026

CVE-2026-40313: MervinPraison PraisonAI · Untrusted Functionality Inclusion

Affects MervinPraison PraisonAISource CVE Database V5

Compare

Not known to be exploited · CVSS 9.1 Critical : upgrade to 4.5.140 as a priority.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score

9.1Critical

How severe the flaw is on the 0–10 CVSS scale.

Contested

Critical score, yet low EPSS after six months

EPSS: 0.3% chance of exploitation in 30 days – higher than 23% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 4.5.140

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 14 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade PraisonAI and mervinpraison/PraisonAI to 4.5.140.

Affected software

Product	Affected	Fixed in
MervinPraisonPraisonAI	Affected <4.5.140	Fixed in 4.5.140
GitHubmervinpraison/PraisonAI`pkg:github/mervinpraison/PraisonAI`Other threats	Affected <4.5.140	Fixed in 4.5.140

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade PraisonAI to version 4.5.140 or later, where this issue has been fixed by properly configuring GitHub Actions workflows to prevent credential leakage. Specifically, workflows should set persist-credentials: false in actions/checkout steps to avoid persisting tokens in .git/config. Since this is a repository configuration issue, patching the workflows is the recommended remediation. Patch status is not explicitly stated as 'official-fix' but the issue is fixed in version 4.5.140, so upgrading is the effective fix.

Description

PraisonAI versions 4.5.139 and below have a critical vulnerability in their GitHub Actions workflows where the default behavior of actions/checkout leads to credential leakage. This occurs because the GITHUB_TOKEN and sometimes ACTIONS_RUNTIME_TOKEN are persisted in the . git/config file and can be inadvertently included in uploaded artifacts. Since PraisonAI is a public repository, any user with read access can download these artifacts and extract these tokens, potentially enabling malicious code injection, supply chain compromise, and theft of repository secrets. The vulnerability is fixed in version 4.5.140.

Impact

The vulnerability allows unauthorized users with read access to the public PraisonAI repository to obtain sensitive GitHub tokens from workflow artifacts. This can lead to malicious code injection, poisoning of releases and package repositories (PyPI/Docker), theft of repository secrets, and a full supply chain compromise affecting all downstream users. The CVSS score of 9.1 reflects a critical impact with high confidentiality and integrity consequences but no direct availability impact.

Summary

CVE-2026-40313 affects PraisonAI, a multi-agent teams system, due to insecure GitHub Actions workflow configurations in versions prior to 4.5.140. The workflows use actions/checkout without setting persist-credentials: false, causing the GITHUB_TOKEN and sometimes ACTIONS_RUNTIME_TOKEN to be saved in the .git/config file. When subsequent workflow steps upload artifacts, these tokens may be included and exposed to any user with read access to the public repository. This exposure allows attackers to push malicious code, poison releases and package repositories, steal secrets, and perform full supply chain compromises. The issue spans multiple workflow and action files and has been addressed in version 4.5.140.

CWE-829Inclusion of Functionality from Untrusted Control Sphere (opens in a new tab)
Base weaknessOWASP Top 10 A08:2025: Software or Data Integrity Failures (opens in a new tab)
The product imports, requires, or includes executable functionality (such as a library) from a source that is outside of the intended control sphere.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Architecture and Design · Enforcement by Conversion
When the set of acceptable objects, such as filenames or URLs, is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames or URLs, and reject all other inputs.
Architecture and Design
For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks…
OWASP Cheat Sheets
Docker Security (opens in a new tab)
Vulnerable Dependency Management (opens in a new tab)
Software Supply Chain Security (opens in a new tab)
Infrastructure as Code (opens in a new tab)
OWASP ASVS 4.0.3
V12.3.6 (opens in a new tab)
V14.2.3 (opens in a new tab)
V14.2.4 (opens in a new tab)
Attack patterns
Serialized Data External Linking (opens in a new tab)
DTD Injection (opens in a new tab)
Local Code Inclusion (opens in a new tab)
PHP Local File Inclusion (opens in a new tab)
Remote Code Inclusion (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 21 Apr 2026, 06:15 UTC

WeaknessesCWE-829

Technical details

References

Community reviews

Related threats