CVE-2026-84832
Deserialization flaw in SEPPmail allows command execution as 'nobody' via privileged API.
Is CVE-2026-84832 being exploited?
Not confirmed. CVE-2026-84832 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.61% probability of exploitation in the next 30 days.
How severe is CVE-2026-84832?
CVE-2026-84832 is rated High with a CVSS score of 8.6. 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-84832?
Yes. A fix has been recorded for CVE-2026-84832. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-84832 affect?
CVE-2026-84832 affects SEPPmail Secure Email Gateway <15.0.6, Privileged REST import/API workflow. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-84832?
Upgrade to 15.0.6+, revoke/rotate privileged API tokens, restrict API access
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated attacker with a privileged API token can trigger deserialization to execute arbitrary commands as 'nobody' via REST import.
Immediate action required
- affected< 15.0.6
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.