Skip to main content
VulnerabilityPublished

CVE-2026-127027: Poste.io is vulnerable to remote code execution in DMARC report processing

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-127027· Critical 9.2

Not known to be exploited · CVSS 9.2 Critical : upgrade to 2.5.22 as a priority.

Data as of 20 Nov 2026, 16:18 UTC

CVSS 4.0 base score
9.2Critical
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (CERT-PL)CVSS 4.09.2
Patch
Available – fixed in 2.5.22
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.

What to do

Upgrade Poste.io to 2.5.22.

Affected software

ProductAffectedFixed in
AnalogicPoste.ioAffected
  • <2.5.22
Fixed in
  • 2.5.22

AI-suggested

Upgrade Poste.io to version 2.5.22 or later, where this vulnerability is fixed. No other mitigations are indicated by the vendor advisory.

Description

Poste.io contains a critical remote code execution vulnerability in its DMARC report processing. Emails sent to dmarc-reports@<domain> are saved without verifying the sender. A root-level script unpacks attachments using unsafe shell commands, allowing command injection via crafted attachment filenames or archive contents. An unauthenticated remote attacker able to send email to the server's port 25 can execute arbitrary commands as root inside the Poste.io container. This vulnerability is fixed in version 2.5.22.

References

Community reviews

Loading reviews…