Skip to content
Web

CVE-2026-61429

8.4
High
EPSS 0.35%Patch availableJul 11, 2026

SSRF via DNS rebinding & redirects in PraisonAI Crawl4AI exposing internal data.

common questions

Is CVE-2026-61429 being exploited?

Not confirmed. CVE-2026-61429 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.35% probability of exploitation in the next 30 days.

How severe is CVE-2026-61429?

CVE-2026-61429 is rated High with a CVSS score of 8.4. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-61429?

Yes. A fix has been recorded for CVE-2026-61429. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-61429 affect?

CVE-2026-61429 affects PraisonAI Crawl4AI, PraisonAI Chromium backend, PraisonAI versions < 1.6.78. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-61429?

Upgrade to PraisonAI 1.6.78+, block DNS rebinding, restrict crawler network and validate redirects

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
PraisonAI Crawl4AIPraisonAI Chromium backendPraisonAI versions < 1.6.78
impact

SSRF lets attacker access internal services, follow redirects, and read sensitive internal responses (canary values) to exfiltrate data or pivot.

action required

Immediate action required

affected versions
MervinPraison PraisonAI
  • affected< 1.6.78
vendor says fixed in1.6.78

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free