CVE-2026-2746
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedSEPPmail Secure Email Gateway before version 15.0.1 does not properly communicate PGP signature verification results, leaving users unable to detect forged emails.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceSEPPmail Secure Email Gateway before version 15.0.1 fails to properly communicate PGP signature verification results to end users. This allows attackers to send forged emails with fake PGP signatures that appear valid to users, as the gateway does not display whether signature verification passed or failed.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 15.0.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify SEPPmail versionAccess the SEPPmail admin interface or check system information to find the installed version of SEPPmail Secure Email Gateway. Look for a version number in the product interface, system logs, or about page.Affected if The installed version is below 15.0.1 (for example, 15.0.0, 14.x.x, or earlier)
-
Verify PGP verification is enabledIn the SEPPmail admin interface, navigate to the email security or PGP settings section. Confirm that PGP signature verification is enabled for incoming emails.Affected if PGP signature verification is turned on in the gateway configuration
-
Test signature verification displaySend a test email with a PGP signature (valid or invalid) through the gateway to a user. Observe whether the email client displays the signature verification status (passed/failed/unsigned) to the end user.Affected if The received email does NOT show clear indication of whether the PGP signature was verified as valid, invalid, or absent - the gateway fails to communicate the verification result
-
Check email headers for verification infoInspect the raw email headers of a PGP-signed message that passed through the gateway. Look for headers or metadata that indicate signature verification status.Affected if No signature verification status information is present in the email headers or body that the user can see
A user is affected if the SEPPmail version is below 15.0.1 AND PGP signature verification is enabled but the gateway does not display verification results to end users, allowing forged signatures to appear valid.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped15.0.1
Upgrade SEPPmail Secure Email Gateway to version 15.0.1 or later to ensure PGP signature verification results are properly communicated to users.
15.0.1
- Obtain the SEPPmail Secure Email Gateway version 15.0.1 from the official vendor download source at downloads.seppmail.com
- Review the SEPPmail upgrade documentation for version 15.0.1
- Perform a backup of the current configuration and any critical email data
- Execute the upgrade process according to vendor documentation, following standard upgrade procedures
- Verify that the upgrade completed successfully
- Confirm that PGP signature verification results are now properly communicated to users
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-2746 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-2746 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data