CVE-2026-47395

MEDIUMPre-NVD 5.55.5
EchelonGraph scoreLOW confidence

This medium-severity CVE scores 5.5 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.0%, top 97% 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: cna:github_m, epss
Elevated
5.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.5Exploit: 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. Prior to version 4.6.40 of PraisonAI, corresponding to version 1.6.40 of praisonaiagents, PraisonAI's direct-prompt CLI automatically expands @url: mentions in raw prompt text before agent execution begins. If a prompt contains @url:, the CLI calls MentionsParser.process(...). The @url: handler then performs a direct urllib.request.urlopen() request to the attacker-controlled URL and returns the response body. That response body is prepended to the final model prompt context. There is no loopback/private-address restriction, no metadata-service restriction, and no approval gate before the fetch. As a result, attacker-influenced prompt text can cause the operator's machine to fetch localhost-only HTTP resources and inject the response into model context. PraisonAI version 4.6.40 and praisonaiagents version 1.6.40 contain a fix.

CVSS v3
5.5
EG Score
5.5(low)
EG Risk
EPSS
2.9%
KEV
Not listed

Published

May 29, 2026

Last Modified

July 21, 2026

Advisory Details (3)

Auto-updated Jul 21, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_pr, github.
github Patch Available🟡 PoC Available

PraisonAI CLI automatically resolves @url mentions in prompt text and can read loopback URLs into model context · Advisory · MervinPraison/PraisonAI · GitHub

https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-5cxw-77wg-jrf3
github_pr 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-47395(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 rangeFixed inDependents
praisonai0.0.1 ... 4.6.9 (731 versions)4.6.40
praisonaiagents0.0.1 ... 1.6.9 (568 versions)1.6.40

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 1× in last 7d / 1× 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-22 14:08 UTCEPSS rescore
  2. 2026-06-14 23:18 UTCEPSS rescore
  3. 2026-06-13 23:00 UTCEPSS rescore
  4. 2026-06-12 23:12 UTCEPSS rescore
  5. 2026-05-29 23:13 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-47395?
CVE-2026-47395 is a medium vulnerability 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, PraisonAI's direct-prompt CLI automatically expands @url: mentions in raw prompt text before agent execution begins. If a prompt contains @url:<http-or-https-url>, the…
When was CVE-2026-47395 disclosed?
CVE-2026-47395 was first published in the National Vulnerability Database on May 29, 2026, with the most recent update on July 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-47395 actively exploited?
CVE-2026-47395 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-47395?
CVE-2026-47395 has a CVSS v3 base score of 5.5 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-47395?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-47395, 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-47395

Explore →

Is Your Infrastructure Affected by CVE-2026-47395?

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