Skip to content
Web

CVE-2026-61824

8.2
High
EPSS 0.23%Patch availableAug 22, 2026

Reflected/DOM XSS in Defuddle extractors allows attacker JS execution when rendered.

common questions

Is CVE-2026-61824 being exploited?

Not confirmed. CVE-2026-61824 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.23% probability of exploitation in the next 30 days.

How severe is CVE-2026-61824?

CVE-2026-61824 is rated High with a CVSS score of 8.2. 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-61824?

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

What does CVE-2026-61824 affect?

CVE-2026-61824 affects Defuddle < 0.19.1, src/extractors/x-article.ts, src/extractors/substack.ts, src/extractors/youtube.ts, and 1 further product or version. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-61824?

Upgrade to Defuddle v0.19.1 and ensure extracted HTML is properly escaped/sanitized before rendering.

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

executive summary
technical analysis
affected
Defuddle < 0.19.1src/extractors/x-article.tssrc/extractors/substack.tssrc/extractors/youtube.tsApps rendering Defuddle output
impact

Cross-site scripting: attacker-controlled JS can execute in victims' browsers when extracted HTML is rendered, enabling session theft, redirect, or supply-chain injection.

action required

Patch when possible

affected versions
kepano defuddle
  • affected< 0.19.1

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