Skip to content
Applications

CVE-2026-82520

8.7
High
EPSS 0.44%Patch availableSep 4, 2026

Decompression-bomb in parsedmarc allows remote DoS via crafted compressed email attachments

common questions

Is CVE-2026-82520 being exploited?

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

How severe is CVE-2026-82520?

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

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

What does CVE-2026-82520 affect?

CVE-2026-82520 affects parsedmarc < 11.0.1, DMARC report processing services, Mailboxes monitored by parsedmarc, Containers/VMs running parsedmarc. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-82520?

Upgrade to parsedmarc 11.0.1 and block/scan compressed email attachments

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

executive summary
technical analysis
affected
parsedmarc < 11.0.1DMARC report processing servicesMailboxes monitored by parsedmarcContainers/VMs running parsedmarc
impact

Unauthenticated attacker sends crafted gzip/ZIP in a DMARC email, forcing unbounded decompression and exhausting RAM, causing parsedmarc crash/DoS.

action required

Patch when possible

affected versions
domainaware parsedmarc
  • affected< 11.0.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