dbcve.org
Secure Email GatewayApplication · Seppmail

CVE-2026-29132

HIGH · 7.5 CVSS v3.1 Published 2026-04-02
Fix available
A fix is available. Upgrade to 15.0.3 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.3 allows an attacker with access to a victim's GINA account to bypass a second-password check and read protected 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 confidence

SEPPmail Secure Email Gateway versions prior to 15.0.3 contain an authentication bypass vulnerability where an attacker who has obtained access to a victim's GINA account can circumvent the second-password check mechanism designed to protect sensitive emails, allowing unauthorized reading of protected email content.

MitigationUpgrade SEPPmail Secure Email Gateway to version 15.0.3 or later. Additionally, review GINA account access controls and implement multi-factor authentication to mitigate credential theft impact.

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
Secure Email GatewayApplication
Affected:< 15.0.3

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. Identify SEPPmail Secure Email Gateway installation
    Locate the SEPPmail Secure Email Gateway installation in your environment and confirm the product name matches SEPPmail Secure Email Gateway.
    Affected if The product is SEPPmail Secure Email Gateway.
  2. Check installed version
    Retrieve the installed version number of SEPPmail Secure Email Gateway and compare it to the affected range of versions prior to 15.0.3.
    Affected if The installed version is lower than 15.0.3.
  3. Verify GINA feature is in use
    Check whether the GINA (Groupware INterface for Secure mail Access) feature or account system is enabled or configured on the installation.
    Affected if GINA accounts or the GINA feature is enabled on the system.
  4. Confirm second-password protection is configured
    Inspect whether the second-password check mechanism for protecting sensitive emails has been configured on the gateway.
    Affected if Second-password protection for sensitive emails is configured and in use.

A user is affected if they are running SEPPmail Secure Email Gateway version lower than 15.0.3 with GINA accounts enabled and second-password protection configured.

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.3 or later
Fixed in 15.0.3
Interim mitigation

Upgrade SEPPmail Secure Email Gateway to version 15.0.3 or later. Additionally, review GINA account access controls and implement multi-factor authentication to mitigate credential theft impact.

Recommended fix High confidence

15.0.3 or later

  1. Identify the current version of SEPPmail Secure Email Gateway by accessing the administration console or running the vendor's version check command.
  2. Navigate to the official download portal at downloads.seppmail.com and download version 15.0.3 or later of SEPPmail Secure Email Gateway.
  3. Review the vendor's upgrade documentation specific to your current version to ensure proper backup of configuration and data.
  4. Apply the upgrade following SEPPmail's documented upgrade procedure (typically via the administration interface or command-line tool provided by the vendor).
  5. After upgrade completion, verify the installation by checking the new version number in the administration console.
  6. Test that the second-password authentication mechanism is functioning correctly by attempting to access protected emails with a GINA account.
Caveat Review release notes for any breaking changes between your current version and 15.0.3; test in non-production environment first if possible

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

Fix this in Secure Email Gateway Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-29132 — 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-29132 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