Email forgery via missing PGP signature tag
Published Mar 4, 2026 · Updated Mar 4, 2026
Improper PGP signature verification in SEPPmail Secure Email Gateway before 15.0.1 allows remote attackers to pass forged emails as authentic. The PGP processing path omits the signature-status tag that should carry verification failure to the recipient, suppressing the visible authenticity warning. Network access is sufficient and requires no account or recipient interaction; SEPPmail has not identified the internal function, and impact is limited to email-origin integrity.
Summary
What happened
Improper PGP signature verification in SEPPmail Secure Email Gateway before 15.0.1 allows remote attackers to pass forged emails as authentic. The PGP processing path omits the signature-status tag that should carry verification failure to the recipient, suppressing the visible authenticity warning. Network access is sufficient and requires no account or recipient interaction; SEPPmail has not identified the internal function, and impact is limited to email-origin integrity.
The record
- CVE
- CVE-2026-2746
- Published
- Mar 4, 2026
- Updated
- Mar 4, 2026
- Vendor
- SEPPmail
- Product
- Secure Email Gateway
- Classifications
- CWE-347, CAPEC-194
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 4, 2026CVE publishedPublication date reported by the CVE source.
- Mar 4, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <15.0.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo