CVE-2026-47390

MEDIUMPre-NVD 5.55.5
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 5.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (6th 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
5.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (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.2%CVSS: 5.5Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

PraisonAI is a multi-agent teams system. Prior to version 4.6.40 of PraisonAI, corresponding to version 1.6.40 of praisonaiagents, spider_tools URL validation can be bypassed using alternate loopback host encodings. The tool contains a URL validation function intended to block local or unsafe targets before fetching attacker-controlled URLs. However, the validation only blocks a small set of exact host strings such as localhost and 127.0.0.1. It does not normalize hostnames, resolve DNS, parse numeric IPv4 variants, or validate the final resolved IP address before making the request. As a result, certain URLs may bypass the protection and still reach loopback services. After the weak validation passes, scrape_page() calls requests.Session.get() on the attacker-controlled URL. This allows an attacker who can influence URLs passed to scrape_page, crawl, or extract_text to induce SSRF requests against loopback-only services. This is a server-side request forgery protection bypass. PraisonAI version 4.6.40 and praisonaiagents version 1.6.40 contain a patch.

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
41
EG Risk 41/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)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 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.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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.
EPSS PROB
0.2%
EPSS %ILE
6th
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 (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-17). 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 or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (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

July 22, 2026

Advisory Details (3)

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

PraisonAI spider_tools SSRF protection bypass via alternate loopback host encodings · Advisory · MervinPraison/PraisonAI · GitHub

https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-5c6w-wwfq-7qqm
GitHub pull request Patch Available

refactor: security batch — 10 hardening fixes

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

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

commit b0d8f777528f (MervinPraison/PraisonAI)

Patch available: MervinPraison/PraisonAI v4.6.126 (contains commit b0d8f777528f)

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

Vendor Advisories for CVE-2026-47390(1)

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

Affected Packages

(2 across 1 ecosystem)
PyPI(2)
PackageVulnerable rangeFix by version rangeDependents
praisonai0.0.1 ... 4.6.9 (731 versions)
  • every version up to 4.6.40: fixed in 4.6.40
—
praisonaiagents0.0.1 ... 1.6.9 (568 versions)
  • every version up to 1.6.40: fixed in 1.6.40
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 31× 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 106 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 6 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-47390?
CVE-2026-47390 is a medium-severity vulnerability; its CVE record was published on May 29, 2026. PraisonAI is a multi-agent teams system. Prior to version 4.6.40 of PraisonAI, corresponding to version 1.6.40 of praisonaiagents, spidertools URL validation can be bypassed using alternate loopback host encodings. The tool contains a URL validation function intended to block local or unsafe…
When was the CVE record for CVE-2026-47390 published?
The CVE record for CVE-2026-47390 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 July 22, 2026; the record at its source may have been updated since.
Is CVE-2026-47390 actively exploited?
CVE-2026-47390 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (6th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-47390?
CVE-2026-47390 has a CVSS base score of 5.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-47390?
A fix for CVE-2026-47390 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-47390 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-47390

Explore →

Is Your Infrastructure Affected by CVE-2026-47390?

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