CVE-2026-48168

CRITICALPre-NVD 10.010.0
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This critical-severity CVE scores 10.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 1.5% (73rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated
10.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 1.5%CVSS: 10.0Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
10.0
EG Score
10.0CRITICALmedium confidence
EG Risk
76
EG Risk 76/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity100% × 45%
The EG Score, 10.0 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
1.5%
EPSS %ILE
73rd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 5, 2026

Last Modified

September 8, 2026

Advisory Details (2)

Auto-updated Oct 14, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

GitHub Actions Claude workflow command injection via unquoted PR branch name · Advisory · MervinPraison/PraisonAI · GitHub

https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-xp85-6wwf-r67c
GitHub commit Patch Available

commit 179cab02dbec (MervinPraison/PraisonAI)

Patch available: MervinPraison/PraisonAI v4.6.150 (contains commit 179cab02dbec)

https://github.com/MervinPraison/PraisonAI/commit/179cab02dbec0c1e9b601507a659

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 13× in last 7d / 48× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 121 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 21 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-14 09:04 UTCEG score recompute
  2. 2026-10-13 16:34 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  3. 2026-10-13 05:54 UTCEG score recompute
  4. 2026-10-12 16:34 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  5. 2026-10-12 16:01 UTCEG score recompute
  6. 2026-10-11 19:44 UTCEG score recompute
  7. 2026-10-11 16:58 UTCEG score recompute
  8. 2026-10-11 14:23 UTCEG score recompute
  9. 2026-10-11 13:49 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  10. 2026-10-10 20:00 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  11. 2026-10-09 20:07 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  12. 2026-10-08 17:12 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  13. 2026-10-07 23:48 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  14. 2026-10-06 23:36 UTCEG score recompute
  15. 2026-10-06 15:18 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  16. 2026-10-05 19:32 UTCEG score recompute
  17. 2026-10-05 17:43 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  18. 2026-10-04 23:29 UTCEG score recompute
  19. 2026-10-04 23:22 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  20. 2026-10-04 05:58 UTCEG score recompute
  21. 2026-10-03 14:25 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  22. 2026-10-03 01:07 UTCEG score recompute
  23. 2026-10-02 09:51 UTCEG score recompute
  24. 2026-10-01 19:50 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  25. 2026-10-01 02:15 UTCEG score recompute
Show 75 more
  1. 2026-09-30 15:03 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  2. 2026-09-29 06:13 UTCEG score recompute
  3. 2026-09-28 13:51 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  4. 2026-09-27 17:39 UTCEG score recompute
  5. 2026-09-27 13:48 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  6. 2026-09-26 15:59 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  7. 2026-09-26 00:27 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  8. 2026-09-25 04:29 UTCEG score recompute
  9. 2026-09-23 21:20 UTCEG score recompute
  10. 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  11. 2026-09-22 21:22 UTCEG score recompute
  12. 2026-09-22 01:23 UTCEG score recompute
  13. 2026-09-20 20:46 UTCEG score recompute
  14. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  15. 2026-09-19 17:38 UTCEG score recompute
  16. 2026-09-18 22:37 UTCEG score recompute
  17. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  18. 2026-09-18 01:06 UTCEG score recompute
  19. 2026-09-17 01:04 UTCEG score recompute
  20. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  21. 2026-09-16 07:27 UTCEG score recompute
  22. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  23. 2026-09-15 06:49 UTCEG score recompute
  24. 2026-09-13 19:27 UTCEG score recompute
  25. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  26. 2026-09-12 17:34 UTCEG score recompute
  27. 2026-09-11 19:16 UTCEG score recompute
  28. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  29. 2026-09-11 14:39 UTCEG score recompute
  30. 2026-09-10 12:45 UTCEG score recompute
  31. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  32. 2026-09-09 06:19 UTCEG score recompute
  33. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  34. 2026-09-07 18:12 UTCEG score recompute
  35. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  36. 2026-09-06 15:53 UTCEG score recompute
  37. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  38. 2026-09-05 18:25 UTCEG score recompute
  39. 2026-09-04 18:00 UTCEG score recompute
  40. 2026-09-04 09:26 UTCEG score recompute
  41. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  42. 2026-09-03 06:42 UTCEG score recompute
  43. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  44. 2026-09-01 19:00 UTCEG score recompute
  45. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  46. 2026-09-01 07:41 UTCEG score recompute
  47. 2026-08-30 23:03 UTCEG score recompute
  48. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  49. 2026-08-30 01:37 UTCEG score recompute
  50. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  51. 2026-08-29 21:20 UTCEG score recompute
  52. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  53. 2026-08-27 19:54 UTCEG score recompute
  54. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  55. 2026-08-26 19:06 UTCEG score recompute
  56. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  57. 2026-08-25 15:13 UTCEG score recompute
  58. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  59. 2026-08-24 17:38 UTCEG score recompute
  60. 2026-08-24 12:55 UTCEG score recompute
  61. 2026-08-23 02:20 UTCEG score recompute
  62. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  63. 2026-08-22 00:35 UTCEG score recompute
  64. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  65. 2026-08-21 03:10 UTCEG score recompute
  66. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  67. 2026-08-19 20:14 UTCEG score recompute
  68. 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  69. 2026-08-18 18:13 UTCEG score recompute
  70. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  71. 2026-08-17 15:07 UTCEG score recompute
  72. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  73. 2026-08-16 17:40 UTCEG score recompute
  74. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  75. 2026-08-16 04:49 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-48168?
CVE-2026-48168 is a critical-severity vulnerability; its CVE record was published on August 5, 2026. 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…
When was the CVE record for CVE-2026-48168 published?
The CVE record for CVE-2026-48168 was published on August 5, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 8, 2026; the record at its source may have been updated since.
Is CVE-2026-48168 actively exploited?
CVE-2026-48168 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.5% probability of exploitation in the next 30 days (73rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-48168?
CVE-2026-48168 has a CVSS base score of 10.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-48168?
A fix for CVE-2026-48168 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-48168

Explore →

Is Your Infrastructure Affected by CVE-2026-48168?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs