Skip to main content
Menu
CVEs

Analogic Poste.io remote code execution in DMARC report processing

Poste.io versions before 2.5.22 are affected, through command injection in DMARC attachment processing. Fixed in 2.5.22.

CVE-2026-127027EUVD-2026-131592GHSA-R4XM-PRG5-2JVJPublished , updated

9.2CriticalCNA
Exploited
No known exploitation
Fix
Fixed in 2.5.22
Who is exposed
Not reported

Summary

Poste.io, made by Analogic, has a remote code execution flaw in how it processes DMARC reports. A remote attacker who can send email to the server on port 25 can run arbitrary commands as root inside the Poste.io container, without logging in and with no user action needed, by sending crafted attachments to the DMARC reports address.

Written by a model

Original description

Poste.io is vulnerable to remote code execution in DMARC report processing. Email sent to dmarc-reports@<domain> is saved without sender verification. Script that runs as root unpacks the attachments using unsafe shell commands, allowing command injection through crafted attachments (e.g. file names or archive contents). A remote unauthenticated attacker who can send an email to the server's port 25 can execute arbitrary commands as root within the Poste.io container.

This issue was fixed in version 2.5.22.

Who should check

Teams running Analogic Poste.io mail server versions before 2.5.22 that accept email on port 25.

“All before 2.5.22”

cert.pl

What to do

Upgrade to a fixed version: 2.5.22.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-127027 (Remote Code Execution in Poste.io), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-127027 (entry last updated 2026-11-20):
Affected:
- Analogic Poste.io: fixed in 2.5.22
Fixed versions: 2.5.22.
Conditions (all must be true for the bug to be hit):
- Poste.io versions before 2.5.22 are affected. (source: https://cert.pl/en/posts/2026/11/CVE-2026-127027/)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-127027 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-127027 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://cert.pl/en/posts/2026/11/CVE-2026-127027
- https://poste.io/
- https://cert.pl/en/posts/2026/11/CVE-2026-127027/
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-127027
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-127027"}.

Affected versions

cve.now Index

27Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity10/10CVSS 9.2, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 72 if added to CISA KEV
  • Would score about 67 if CISA's SSVC rates exploitation active
  • Would score about 32 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Posted on X by cve.now
  4. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: total

  5. Record last updated

Evidence 4

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
Linkposte.io · poste.io
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-127027
RecordNVD · CVE-2026-127027
Other links 1
Linkcert.pl · en/posts/2026/11/CVE-2026-127027

Questions about CVE-2026-127027

Is CVE-2026-127027 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

The bug is a command injection in how Poste.io processes DMARC attachments. It can let an attacker run arbitrary commands as root inside the Poste.io container.

Source: cert.pl

Which versions are affected by CVE-2026-127027?

Poste.io: before 2.5.22.

Source: cve.now feed data

Am I affected, and how do I check?

All Poste.io versions before 2.5.22 are affected. To check a installation, look at the Poste.io version it runs and compare it with 2.5.22.

Source: cert.pl

How do I fix CVE-2026-127027?

Upgrade Poste.io to version 2.5.22, which contains the fix.

Source: cert.pl

No corrections so far. Something wrong on this page? Report an error.