CVE-2026-44338

HIGHNVD 7.37.3—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.3 under NVD CVSS v3. EPSS exploit probability: 26.8%, top 2% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
7.3
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 27%CVSS: 7.3Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

PraisonAI is a multi-agent teams system. From version 2.5.6 to before version 4.6.34, PraisonAI ships a legacy Flask API server with authentication disabled by default. When that server is used, any caller that can reach it can access /agents and trigger the configured agents.yaml workflow through /chat without providing a token. This issue has been patched in version 4.6.34.

CVSS v3
7.3
EG Score
7.3(medium)
EPSS
97.8%
KEV
Not listed

Published

May 8, 2026

Last Modified

May 8, 2026

Advisory Details (1)

Auto-updated May 8, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

PraisonAI ships and generates a legacy API server with authentication disabled by default, allowing unauthenticated workflow execution · Advisory · MervinPraison/PraisonAI · GitHub

https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-6rmh-7xcm-cpxj

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
praisonai2.5.6 ... 4.6.9 (348 versions)4.6.34—

Weakness Classification(3)

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

Data Freshness Timeline

(refreshed 5× in last 7d / 35× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

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

Publicly available exploits

(1 reference)

Working exploit code is in the public domain. Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Nucleihttp/cves/2026/cve-2026-44338.yaml
    First seen Jan 1, 2026

    PraisonAI - Authentication Bypass

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-44338?
CVE-2026-44338 is a high vulnerability published on May 8, 2026. PraisonAI is a multi-agent teams system. From version 2.5.6 to before version 4.6.34, PraisonAI ships a legacy Flask API server with authentication disabled by default. When that server is used, any caller that can reach it can access /agents and trigger the configured agents.yaml workflow through…
When was CVE-2026-44338 disclosed?
CVE-2026-44338 was first published in the National Vulnerability Database on May 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-44338 actively exploited?
CVE-2026-44338 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 97.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-44338?
CVE-2026-44338 has a CVSS v3 base score of 7.3 (NVD).
How do I remediate CVE-2026-44338?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44338, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-44338?

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

Start Free Scan →Browse All CVEs