CVE-2026-55523

HIGHPre-NVD 7.77.7—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 70% 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, secondary
Elevated
7.7EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.7Exploit: Elevated riskExposed: 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. In versions 1.5.128 through 1.6.57, the praisonaiagents.tools.web_crawl_tools.web_crawl() function is vulnerable to server-side request forgery. While it validates the initially supplied URL and blocks direct loopback and private destinations, its default httpx fallback uses httpx.Client(follow_redirects=True) and does not revalidate intermediate or final redirect targets. An attacker who can influence a URL passed to web_crawl(), directly or through an agent or tool workflow, can supply an attacker-controlled public URL that passes the initial host check and then redirects to loopback, private-network, or cloud metadata endpoints reachable from the host, with the redirected response body returned in the web_crawl() result. This constitutes an incomplete fix and patch bypass for the previously disclosed web_crawl SSRF class (GHSA-qq9r-63f6-v542 / CVE-2026-40160 and GHSA-8f4v-xfm9-3244), since the guard validates only the requested URL and not the destination actually fetched after redirection. This issue has been fixed in version 1.6.58.

CVSS v3
7.7
EG Score
7.7(medium)
EG Risk
66(Attend)
EG Risk 66/100SSVC: Attend

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
Severity77% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
30%
KEV
Not listed

Published

August 5, 2026

Last Modified

September 8, 2026

Advisory Details (1)

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

web_crawl SSRF Protection Bypass via Unchecked Redirect Targets · Advisory · MervinPraison/PraisonAI · GitHub

https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-8hjw-25cg-g52h

Vendor Advisories for CVE-2026-55523(1)

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

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
praisonaiagents1.5.128 ... 1.6.9 (78 versions)1.6.58—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 51× 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-09-19 07:36 UTCEG score recompute
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-18 05:02 UTCEG score recompute
  4. 2026-09-17 19:31 UTCEPSS rescore
  5. 2026-09-17 01:04 UTCEG score recompute
  6. 2026-09-16 14:08 UTCEPSS rescore
  7. 2026-09-16 05:24 UTCEG score recompute
  8. 2026-09-16 05:15 UTCEPSS rescore
  9. 2026-09-15 16:13 UTCEG score recompute
  10. 2026-09-15 03:11 UTCEPSS rescore
  11. 2026-09-13 22:56 UTCEG score recompute
  12. 2026-09-13 16:47 UTCEPSS rescore
  13. 2026-09-12 20:34 UTCEG score recompute
  14. 2026-09-11 18:12 UTCEG score recompute
  15. 2026-09-11 14:53 UTCEPSS rescore
  16. 2026-09-10 15:50 UTCEG score recompute
  17. 2026-09-10 09:35 UTCEPSS rescore
  18. 2026-09-09 10:44 UTCEG score recompute
  19. 2026-09-08 22:01 UTCEPSS rescore
  20. 2026-09-07 18:11 UTCEG score recompute
  21. 2026-09-07 16:01 UTCEPSS rescore
  22. 2026-09-06 20:47 UTCEG score recompute
  23. 2026-09-06 13:47 UTCEPSS rescore
  24. 2026-09-05 18:24 UTCEG score recompute
  25. 2026-09-05 03:45 UTCEG score recompute
Show 56 more
  1. 2026-09-04 09:26 UTCEG score recompute
  2. 2026-09-04 05:06 UTCEPSS rescore
  3. 2026-09-03 06:38 UTCEG score recompute
  4. 2026-09-02 14:12 UTCEPSS rescore
  5. 2026-09-01 19:00 UTCEG score recompute
  6. 2026-09-01 13:54 UTCEPSS rescore
  7. 2026-09-01 04:40 UTCEPSS rescore
  8. 2026-08-30 23:41 UTCEG score recompute
  9. 2026-08-30 19:17 UTCEPSS rescore
  10. 2026-08-30 10:31 UTCEG score recompute
  11. 2026-08-30 01:22 UTCEPSS rescore
  12. 2026-08-29 21:19 UTCEG score recompute
  13. 2026-08-28 21:41 UTCEPSS rescore
  14. 2026-08-28 02:52 UTCEG score recompute
  15. 2026-08-27 14:25 UTCEPSS rescore
  16. 2026-08-27 00:28 UTCEG score recompute
  17. 2026-08-26 14:46 UTCEPSS rescore
  18. 2026-08-25 21:51 UTCEG score recompute
  19. 2026-08-25 13:49 UTCEPSS rescore
  20. 2026-08-24 19:23 UTCEG score recompute
  21. 2026-08-23 03:41 UTCEG score recompute
  22. 2026-08-23 00:19 UTCEPSS rescore
  23. 2026-08-22 01:20 UTCEG score recompute
  24. 2026-08-21 23:49 UTCEPSS rescore
  25. 2026-08-20 22:57 UTCEG score recompute
  26. 2026-08-20 22:55 UTCEPSS rescore
  27. 2026-08-19 20:36 UTCEG score recompute
  28. 2026-08-19 17:04 UTCEPSS rescore
  29. 2026-08-18 18:13 UTCEG score recompute
  30. 2026-08-18 13:48 UTCEPSS rescore
  31. 2026-08-17 15:07 UTCEG score recompute
  32. 2026-08-17 13:47 UTCEPSS rescore
  33. 2026-08-17 01:56 UTCEG score recompute
  34. 2026-08-16 14:56 UTCEPSS rescore
  35. 2026-08-16 12:45 UTCEG score recompute
  36. 2026-08-16 02:14 UTCEPSS rescore
  37. 2026-08-15 10:23 UTCEG score recompute
  38. 2026-08-15 01:30 UTCEPSS rescore
  39. 2026-08-14 08:01 UTCEG score recompute
  40. 2026-08-13 22:00 UTCEPSS rescore
  41. 2026-08-12 16:28 UTCEG score recompute
  42. 2026-08-12 13:51 UTCEPSS rescore
  43. 2026-08-11 14:07 UTCEG score recompute
  44. 2026-08-11 00:56 UTCEG score recompute
  45. 2026-08-11 00:00 UTCEPSS rescore
  46. 2026-08-09 22:35 UTCEG score recompute
  47. 2026-08-09 13:46 UTCEPSS rescore
  48. 2026-08-08 20:13 UTCEG score recompute
  49. 2026-08-08 16:37 UTCEPSS rescore
  50. 2026-08-07 17:51 UTCEG score recompute
  51. 2026-08-06 15:29 UTCEG score recompute
  52. 2026-08-06 14:46 UTCEG score recompute
  53. 2026-08-06 13:47 UTCEPSS rescore
  54. 2026-08-05 20:32 UTCEG score recompute
  55. 2026-08-05 19:40 UTCEG score recompute
  56. 2026-08-05 19:40 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-55523?
CVE-2026-55523 is a high vulnerability published on August 5, 2026. PraisonAI is a multi-agent teams system. In versions 1.5.128 through 1.6.57, the praisonaiagents.tools.webcrawltools.webcrawl() function is vulnerable to server-side request forgery. While it validates the initially supplied URL and blocks direct loopback and private destinations, its default httpx…
When was CVE-2026-55523 disclosed?
CVE-2026-55523 was first published in the National Vulnerability Database on August 5, 2026, with the most recent update on September 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-55523 actively exploited?
CVE-2026-55523 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 70.0% of all scored CVEs.
What is the CVSS score of CVE-2026-55523?
CVE-2026-55523 has a CVSS v3 base score of 7.7 (NVD).
How do I remediate CVE-2026-55523?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55523, 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-55523

Explore →

Is Your Infrastructure Affected by CVE-2026-55523?

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

Start Free Scan →Browse All CVEs