Skip to main content
VulnerabilityPublished

CVE-2026-2746: SEPPmail Secure Email Gateway · Improper Verification of Cryptographic Signature

Affects SEPPmail Secure Email GatewaySource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.9 Medium : upgrade to 15.0.1 when convenient.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 15.0.1
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Mar 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 30 Oct 2026.

What to do

Upgrade SEPPmail Secure Email Gateway to 15.0.1.

Affected software

ProductAffectedFixed in
SEPPmailSecure Email GatewayAffected
  • <15.0.1
Fixed in
  • 15.0.1

AI-suggested

To mitigate CVE-2026-2746, organizations should immediately upgrade SEPPmail Secure Email Gateway to version 15.0.1 or later, where the signature verification communication issue is resolved. In parallel, implement enhanced email security controls such as deploying complementary email authentication standards (SPF, DKIM, DMARC) to reduce reliance solely on PGP signatures. Conduct regular audits of email gateway logs and signature verification results to detect anomalies. Train users to recognize signs of forged or suspicious emails despite signature indicators, emphasizing caution with unexpected or unusual messages. Consider deploying additional email security solutions that perform independent signature validation and alerting. Establish incident response procedures specifically addressing forged email detection and reporting. Maintain up-to-date threat intelligence feeds to monitor emerging exploits targeting this vulnerability. Finally, coordinate with SEPPmail support and security advisories to stay informed about patches and mitigations.

Description

SEPPmail Secure Email Gateway before version 15.0.1 does not properly communicate PGP signature verification results, leaving users unable to detect forged emails.

References

Community reviews

Loading reviews…