---
id: CVE-2026-48168
title: PraisonAI is a multi-agent teams system
summary: >-
  PraisonAI is a multi-agent teams system. In versions prior to 4.6.40, the
  bundled Claude GitHub Actions workflow is vulnerable to command injection
  because it embeds an attacker-controlled pull request branch name into a Bash
  run: block …
severity: critical
cvss: 10
cvssVector: 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H'
cwe:
  - CWE-862
published: '2026-08-05'
updated: '2026-09-08'
sourceUpdated: '2026-09-08T20:51:43.490'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-48168'
references:
  - url: >-
      https://github.com/MervinPraison/PraisonAI/commit/179cab02dbec0c1e9b601507a659
    label: security-advisories@github.com
  - url: >-
      https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-xp85-6wwf-r67c
    label: security-advisories@github.com
  - url: >-
      https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-xp85-6wwf-r67c
    label: 134c704f-9b21-4f2e-91b3-4a467353bcc0
tags:
  - nvd
epss: 0.01503
epssPercentile: 0.73198
ingestedAt: '2026-09-08T21:11:12.268Z'
---

## Overview

PraisonAI is a multi-agent teams system. In versions prior to 4.6.40, the bundled Claude GitHub Actions workflow is vulnerable to command injection because it embeds an attacker-controlled pull request branch name into a Bash run: block without quoting or validation. Additionally, the workflow allows any @claude comment to trigger the job regardless of whether the commenter is a trusted collaborator. An outside contributor can open a pull request from a fork whose branch name contains shell metacharacters and comment @claude, causing Bash to execute arbitrary shell code in the GitHub Actions runner. Because these commands run in a job holding a GitHub App token with write permissions, OIDC access, and gh/git access, the injection can be chained through $GITHUB_PATH to compromise later privileged steps, enabling repository writes, pull request and issue manipulation, or OIDC-token abuse. This issue has been fixed in version 4.6.40.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
