CVE-2026-58653

MEDIUMPre-NVD 4.34.3—
EchelonGraph scoreHIGH confidence

Score 4.3 from GitHub Security Advisory published 2026-07-02. a secondary CVSS source baseline 4.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
4.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 4.3Exploit: NoneExposed: 0

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

PraisonAI before 0.1.7 fails to validate that project_id in issue create and update request bodies belongs to the URL workspace. An attacker can create issues referencing projects from other workspaces, causing cross-tenant data pollution in project statistics aggregation without workspace constraints.

CVSS v3
4.3
EG Score
4.3(high)
EPSS
5.4%
KEV
Not listed

Published

July 2, 2026

Last Modified

July 2, 2026

Advisory Details (2)

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

Authorization Bypass Through User-Controlled Key in praisonai-platform · Advisory · MervinPraison/PraisonAI · GitHub

Affected: 0.1.4 (

https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-2fjj-qqg8-fg7x
generic

PraisonAI - Authorization Bypass via Unvalidated project_id in Issue Create/Update | Advisories | VulnCheck

https://www.vulncheck.com/advisories/praisonai-authorization-bypass-via-unvalidated-project-id-in-issue-create-update

Vendor Advisories for CVE-2026-58653(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 21× in last 7d / 21× 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-07 06:20 UTCEG score recompute
  2. 2026-07-07 06:20 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 08:20 UTCEG score recompute
  6. 2026-07-06 08:19 UTCGHSA enrichment
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-05 10:20 UTCEG score recompute
  10. 2026-07-05 10:20 UTCGHSA enrichment
  11. 2026-07-05 02:31 UTCEPSS rescore
  12. 2026-07-05 02:30 UTCEPSS rescore
  13. 2026-07-04 12:21 UTCEG score recompute
  14. 2026-07-04 12:21 UTCGHSA enrichment
  15. 2026-07-04 06:31 UTCEPSS rescore
  16. 2026-07-04 06:31 UTCEPSS rescore
  17. 2026-07-03 14:23 UTCEG score recompute
  18. 2026-07-03 14:22 UTCGHSA enrichment
  19. 2026-07-02 20:05 UTCNVD updateCVSS v4 → 5.3
  20. 2026-07-02 16:24 UTCEG score recompute
  21. 2026-07-02 16:24 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-58653?
CVE-2026-58653 is a medium vulnerability published on July 2, 2026. PraisonAI before 0.1.7 fails to validate that project_id in issue create and update request bodies belongs to the URL workspace. An attacker can create issues referencing projects from other workspaces, causing cross-tenant data pollution in project statistics aggregation without workspace…
When was CVE-2026-58653 disclosed?
CVE-2026-58653 was first published in the National Vulnerability Database on July 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-58653 actively exploited?
CVE-2026-58653 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 5.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-58653?
CVE-2026-58653 has a CVSS v3 base score of 4.3 (NVD).
How do I remediate CVE-2026-58653?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-58653, 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

Explore the affected products and dependency analysis for CVE-2026-58653

Explore →

Is Your Infrastructure Affected by CVE-2026-58653?

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

Start Free Scan →Browse All CVEs