CVE-2026-47410

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-05-29. A secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Elevated

Also known asEUVD-2026-46324 (ENISA EUVD) · GHSA-3qg8-5g3r-79v5 (GitHub Security Advisories) · PYSEC-2026-479 (OSV.dev)Source: ENISA EUVD

9.8EG
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: 0.4%CVSS: 9.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

PraisonAI Platform is the platform layer for the PraisonAI multi-agent teams system. Versions prior to 0.1.4 have an insecure default cryptographic key. The JWT signing secret defaults to the hardcoded literal "dev-secret-change-me" when PLATFORM_JWT_SECRET is unset. A safety check exists but only fires when PLATFORM_ENV != "dev"; the default value of PLATFORM_ENV is "dev", so the check is silently bypassed in any deployment that does not explicitly opt out. The attacker reads the literal from this public source file, mints a JWT with arbitrary sub and email claims, and authenticates as any existing user (including workspace owners and admins). PraisonAI Platform version 0.1.4 patches the issue.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
75
EG Risk 75/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
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
0.4%
EPSS %ILE
39th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

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.

The score's inputs: 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

May 29, 2026

Last Modified

October 24, 2026

Advisory Details (3)

Auto-updated Nov 9, 2026
Patch available. Sources: github, github_commit, github_pr.
GitHub advisoryMentions a patch (unverified)

praisonai-platform: JWT signing key defaults to hardcoded "dev-secret-change-me", allowing token forgery for any user when PLATFORM_ENV is unset · Advisory · MervinPraison/PraisonAI · GitHub

https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-3qg8-5g3r-79v5
GitHub pull request Patch Available

refactor: security batch 2 — platform IDOR and deploy hardening

Patch available: MervinPraison/PraisonAI v4.6.160 (PR #1685 merged 2026-05-19)

https://github.com/MervinPraison/PraisonAI/pull/1685
GitHub commit Patch Available

commit ef79b7a05617 (MervinPraison/PraisonAI)

Patch available: MervinPraison/PraisonAI v4.6.160 (contains commit ef79b7a05617)

https://github.com/MervinPraison/PraisonAI/commit/ef79b7a0561796ad9807f0f09538c25cc78d3619

Vendor Advisories for CVE-2026-47410(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
pippraisonai-platform @ 0.1.4 (fixes <= 0.1.2)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
praisonai-platform0.1.0, 0.1.1, 0.1.2, 0.1.3
  • every version up to 0.1.4: fixed in 0.1.4
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 45× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 184 rows 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 84 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-47410?
CVE-2026-47410 is a critical-severity vulnerability; its CVE record was published on May 29, 2026. PraisonAI Platform is the platform layer for the PraisonAI multi-agent teams system. Versions prior to 0.1.4 have an insecure default cryptographic key. The JWT signing secret defaults to the hardcoded literal "dev-secret-change-me" when PLATFORM_JWT_SECRET is unset. A safety check exists but only…
When was the CVE record for CVE-2026-47410 published?
The CVE record for CVE-2026-47410 was published on May 29, 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 October 24, 2026; the record at its source may have been updated since.
Is CVE-2026-47410 actively exploited?
CVE-2026-47410 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (39th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-47410?
CVE-2026-47410 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-47410?
A fix for CVE-2026-47410 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-47410 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-47410

Explore →

Is Your Infrastructure Affected by CVE-2026-47410?

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

Book a Demo →Browse All CVEs