dbcve.org
Secure Email GatewayApplication · Seppmail

CVE-2026-29134

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 external user to modify GINA webdomain metadata and bypass per-domain restrictions.

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.3 contain a broken access control vulnerability where external (unauthenticated) users can modify GINA webdomain metadata. This allows attackers to bypass per-domain restrictions and potentially modify email routing or web domain configurations.

MitigationUpgrade to SEPPmail Secure Email Gateway version 15.0.3 or later to obtain the vendor patch. Review access controls on GINA webdomain management interfaces as a precautionary measure.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 version
    Access the admin console or check system information on the SEPPmail server to determine the installed version. Look for version details in the admin UI or use the command line interface to retrieve version information if available.
    Affected if The installed version is any version before 15.0.3 (e.g., 15.0.2, 14.x, earlier releases).
  2. Determine if GINA webdomain management is accessible
    Review the network configuration and firewall rules to determine whether the GINA webinterface is exposed to external/untrusted networks. Check if the management interface listens on externally reachable network interfaces.
    Affected if The GINA webdomain management interface is accessible from external/unauthenticated networks without requiring authentication.
  3. Inspect access control configuration for webdomain metadata
    Examine the GINA configuration settings and access control lists (ACLs) for the webdomain management feature. Look for any configuration that controls who can modify GINA webdomain metadata.
    Affected if External or unauthenticated users can submit requests to modify GINA webdomain metadata without being denied or requiring authentication.

A user is affected if their SEPPmail Secure Email Gateway version is below 15.0.3 AND the GINA webdomain management interface is externally accessible without proper authentication controls.

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 to SEPPmail Secure Email Gateway version 15.0.3 or later to obtain the vendor patch. Review access controls on GINA webdomain management interfaces as a precautionary measure.

Recommended fix High confidence

15.0.3

  1. 1. Check the current SEPPmail Secure Email Gateway version using the administrative interface or command line
  2. 2. Download Secure Email Gateway version 15.0.3 from the official vendor source (downloads.seppmail.com)
  3. 3. Review the upgrade documentation provided by SEPPmail
  4. 4. Perform the upgrade following the vendor's recommended upgrade procedure
  5. 5. Verify the upgrade was successful and the version shows 15.0.3
  6. 6. Confirm the vulnerability is remediated by testing that external users can no longer modify GINA webdomain metadata

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

Fix this in Secure Email Gateway Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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