Security readout for executives and security teams
Plain-English summary
A malicious outside contributor could abuse PraisonAI’s bundled Claude workflow to run unauthorized commands in a GitHub Actions runner. The job carries powerful repository and identity permissions, creating risk of repository changes, issue or pull-request manipulation, and OIDC-token abuse. PraisonAI versions before 4.6.40 are affected.
Executive priority
Prioritize immediate remediation wherever the workflow is enabled, especially in repositories accepting public fork pull requests. The maximum CVSS score and privileged runner context support emergency handling. If exposure is confirmed, upgrade or disable the workflow promptly and investigate historical runs before restoring normal operation.
Technical view
The workflow places an attacker-controlled pull-request branch name into an unquoted, unvalidated Bash run block. Any commenter could trigger the job with @claude, without collaborator verification. Shell metacharacters in a fork branch name could therefore execute commands and modify $GITHUB_PATH, influencing later privileged steps holding GitHub App, write, OIDC, gh, and git access.
Likely exposure
Exposure requires PraisonAI before 4.6.40 and use of the vulnerable bundled Claude GitHub Actions workflow. Repositories accepting fork pull requests are particularly relevant because an outside contributor could supply the branch name and trigger the job. The bundle does not establish how many deployments enabled this workflow.
Exploitation context
The described attack is remote, low-complexity, and requires neither existing privileges nor victim interaction according to the supplied CVSS assessment. However, the source bundle marks this CVE as absent from KEV and provides no evidence of active exploitation. Treat the attack path as credible, but do not claim observed exploitation.
Researcher notes
The supplied record attributes the authorization weakness to CWE-862 and describes command injection through unsafe Bash interpolation. The critical impact depends on the vulnerable workflow running with the stated privileges and on later privileged steps being influenced. Validate actual workflow configuration and permissions per repository. No affected products beyond MervinPraison PraisonAI, or versions beyond those stated, are established.
Mitigation direction
- Upgrade PraisonAI to version 4.6.40 or later.
- Disable the affected Claude workflow until the upgrade is completed.
- Restrict workflow triggering to trusted collaborators using vendor-supported controls.
- Review and minimize GitHub App, repository-write, and OIDC permissions assigned to the job.
- Consult the GitHub advisory and corrected commit for vendor-approved remediation details.
Validation and detection
- Inventory repositories using PraisonAI versions earlier than 4.6.40.
- Confirm whether the bundled Claude workflow is present and enabled.
- Verify branch-name handling is quoted or validated after remediation.
- Verify untrusted commenters cannot trigger privileged workflow execution.
- Review workflow history for suspicious fork branches, @claude triggers, and unexpected repository changes.
- Investigate unexpected path modifications, privileged downstream activity, or OIDC use associated with affected runs.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-862: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-48168 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 10 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H3.96GitHub_MVulnerability scoring details
Base CVSS 3.1 score
10CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-xp85-6wwf-r67cCVE reference, GitHub_M · x_refsource_CONFIRM
- https://github.com/MervinPraison/PraisonAI/commit/179cab02dbec0c1e9b601507a659CVE reference, GitHub_M · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Missing Authorization
Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.