dbcve.org
SeppmailApplication

CVE-2026-2747

HIGH · 7.5 CVSS v3.1 Published 2026-03-04
Fix available
A fix is available. Upgrade to 15.0.1 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
SEPPmail Secure Email Gateway before version 15.0.1 decrypts inline PGP messages without isolating them from surrounding unencrypted content, allowing exposure of sensitive information to an unauthorized actor.

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 confidence

SEPPmail Secure Email Gateway versions before 15.0.1 contain a vulnerability where inline PGP encrypted messages are decrypted but the decrypted content is not properly isolated from surrounding unencrypted content within the email. This can cause sensitive information that users intended to be encrypted to be exposed to unauthorized actors.

MitigationUpgrade SEPPmail Secure Email Gateway to version 15.0.1 or later, which properly isolates decrypted PGP content from surrounding unencrypted portions of the email.

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
SeppmailApplication
Affected:< 15.0.1

CVSS 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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Determine SEPPmail Secure Email Gateway version
    Locate the installed version of SEPPmail Secure Email Gateway. This is typically visible in the admin interface under System > Status or can be obtained via command line tools provided by the product (such as 'seppmail --version' or viewing /proc/version if applicable to your installation). Compare the installed version number against the affected range: versions before 15.0.1 are vulnerable.
    Affected if Installed version is below 15.0.1
  2. Verify PGP inline encryption is in use
    Check the SEPPmail configuration for PGP encryption settings. Look for PGP inline encryption being enabled in the email policy or gateway settings. This can typically be found in the admin console under Encryption settings or by reviewing the configuration files that control PGP handling.
    Affected if PGP inline encryption is enabled in the gateway configuration
  3. Inspect processed emails for decrypted content exposure
    Review email logs or examine processed emails that were handled by the gateway. Look for instances where inline PGP encrypted messages were decrypted but remain adjacent to or mixed with unencrypted portions of the same email. Check email headers and body content for plaintext that should have remained encrypted.
    Affected if Emails contain decrypted PGP content that is not properly isolated from surrounding unencrypted portions, with plaintext sensitive data visible alongside or after decrypted sections

A system is affected if it runs SEPPmail Secure Email Gateway version below 15.0.1 with PGP inline encryption enabled, and processed emails show decrypted content improperly exposed alongside unencrypted portions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 15.0.1 or later
Fixed in 15.0.1
Interim mitigation

Upgrade SEPPmail Secure Email Gateway to version 15.0.1 or later, which properly isolates decrypted PGP content from surrounding unencrypted portions of the email.

Recommended fix High confidence

15.0.1

  1. Obtain SEPPmail Secure Email Gateway version 15.0.1 or later from the official download source at downloads.seppmail.com
  2. Review SEPPmail upgrade documentation specific to your current version before proceeding
  3. Execute the standard SEPPmail upgrade procedure according to vendor documentation
  4. After upgrade, verify that inline PGP messages are properly isolated during decryption
  5. Confirm the new version is running: 15.0.1 or later

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Seppmail Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-2747 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-2747 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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