CVE-2026-61429

HIGHPre-NVD 8.58.5—
EchelonGraph scoreHIGH confidence

Score 8.5 from GitHub Security Advisory (severity: HIGH) published 2026-07-11. a secondary CVSS source baseline 8.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this weekElevated
8.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.5Exploit: NoneExposed: 0

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

PraisonAI versions before 1.6.78 contain a server-side request forgery vulnerability in the Crawl4AI/Chromium backend that allows attackers to bypass SSRF validation by exploiting DNS rebinding and HTTP redirects. Attackers can craft URLs that resolve to internal services after the initial validation check, enabling the headless browser to follow redirects and read internal responses including sensitive canary values.

CVSS v3
8.5
EG Score
8.5(high)
EPSS
12.6%
KEV
Not listed

Published

July 11, 2026

Last Modified

July 13, 2026

Advisory Details (2)

Auto-updated Jul 11, 2026
🔬 Proof of concept available. Patch available. Sources: github.
generic

PraisonAI before 1.6.78 SSRF via Crawl4AI Chromium backend | Advisories | VulnCheck

https://www.vulncheck.com/advisories/praisonai-before-ssrf-via-crawl4ai-chromium-backend
github Patch Available🟡 PoC Available

Crawl4AI/Chromium backend is also affected by the `web_crawl` SSRF validation bypass · Advisory · MervinPraison/PraisonAI · GitHub

https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-6g59-gm2v-qhvq

Vendor Advisories for CVE-2026-61429(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 15× in last 7d / 15× 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-14 07:05 UTCEG score recompute
  2. 2026-07-14 07:05 UTCGHSA enrichment
  3. 2026-07-13 22:31 UTCEPSS rescore
  4. 2026-07-13 17:57 UTCEG score recompute
  5. 2026-07-13 17:57 UTCGHSA enrichment
  6. 2026-07-13 06:13 UTCEPSS rescore
  7. 2026-07-13 06:13 UTCEPSS rescore
  8. 2026-07-13 04:51 UTCEG score recompute
  9. 2026-07-13 04:51 UTCGHSA enrichment
  10. 2026-07-12 15:45 UTCEG score recompute
  11. 2026-07-12 15:45 UTCGHSA enrichment
  12. 2026-07-12 02:40 UTCEG score recompute
  13. 2026-07-12 02:39 UTCGHSA enrichment
  14. 2026-07-11 13:32 UTCEG score recompute
  15. 2026-07-11 13:32 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-61429?
CVE-2026-61429 is a high vulnerability published on July 11, 2026. PraisonAI versions before 1.6.78 contain a server-side request forgery vulnerability in the Crawl4AI/Chromium backend that allows attackers to bypass SSRF validation by exploiting DNS rebinding and HTTP redirects. Attackers can craft URLs that resolve to internal services after the initial…
When was CVE-2026-61429 disclosed?
CVE-2026-61429 was first published in the National Vulnerability Database on July 11, 2026, with the most recent update on July 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-61429 actively exploited?
CVE-2026-61429 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 12.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-61429?
CVE-2026-61429 has a CVSS v3 base score of 8.5 (NVD).
How do I remediate CVE-2026-61429?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-61429, 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-61429

Explore →

Is Your Infrastructure Affected by CVE-2026-61429?

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

Start Free Scan →Browse All CVEs