CVE-2026-55524

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 91% 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.5EG
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.5Exploit: 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 prior to 1.6.58, the web_crawl tool performs its SSRF check only on the initially supplied URL, allowing the protection to be bypassed so the tool connects to attacker-chosen internal destinations. The check resolves the hostname once with socket.gethostbyname and rejects private/loopback/link-local results, but then passes the URL to a fetcher using httpx.Client(follow_redirects=True) (or urllib.request.urlopen when httpx is absent, which also follows redirects) that re-resolves the hostname at connect time with no further validation. This validate-here/fetch-there gap is exploitable through both HTTP redirects and DNS rebinding. If an attacker can influence URLs passed to web_crawl(), directly or through an agent/tool workflow, they can cause the PraisonAI host to fetch loopback, private-network, or cloud metadata endpoints reachable from that host, with the response body returned in the web_crawl() result. This issue has been fixed in version 1.6.58.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
50(Track)
EG Risk 50/100SSVC: Track

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
Severity75% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
9%
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

SSRF in web_crawl tool via redirect-following and DNS rebinding (validate-then-fetch gap) · Advisory · MervinPraison/PraisonAI · GitHub

https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-vg6p-v9vm-6fgj

Vendor Advisories for CVE-2026-55524(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
praisonaiagents0.0.1 ... 1.6.9 (585 versions)1.6.58—

Weakness Classification(2)

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

Data Freshness Timeline

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-55524?
CVE-2026-55524 is a high vulnerability published on August 5, 2026. PraisonAI is a multi-agent teams system. In versions prior to 1.6.58, the webcrawl tool performs its SSRF check only on the initially supplied URL, allowing the protection to be bypassed so the tool connects to attacker-chosen internal destinations. The check resolves the hostname once with…
When was CVE-2026-55524 disclosed?
CVE-2026-55524 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-55524 actively exploited?
CVE-2026-55524 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 90.6% of all scored CVEs.
What is the CVSS score of CVE-2026-55524?
CVE-2026-55524 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-55524?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55524, 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-55524

Explore →

Is Your Infrastructure Affected by CVE-2026-55524?

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

Start Free Scan →Browse All CVEs