CVE-2026-29131
CVE-2026-29131 is a high-severity vulnerability in Seppmail Secure Email Gateway with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-90.
Key facts
- Severity: High (CVSS 3.x base score 7.5)
- CVSS v4: 4.9
- EPSS exploit prediction: 0% (13th percentile)
- Actively exploited: Not listed in CISA KEV
- EU (EUVD) id: EUVD-2026-18142
- Weakness: CWE-90
- Affected product: Seppmail Secure Email Gateway
- Published:
- Last modified:
Description
SEPPmail Secure Email Gateway before version 15.0.3 allows attackers with a specially crafted email address to read the contents of emails encrypted for other users.
Frequently asked questions
- What is CVE-2026-29131?
- SEPPmail Secure Email Gateway before version 15.0.3 allows attackers with a specially crafted email address to read the contents of emails encrypted for other users.
- How severe is CVE-2026-29131?
- CVE-2026-29131 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
- Is CVE-2026-29131 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (13th percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2026-29131?
- CVE-2026-29131 affects Seppmail Secure Email Gateway. See the affected-products list for the exact vulnerable versions.
- How do I fix CVE-2026-29131?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
- Does CVE-2026-29131 have an EU (EUVD) identifier?
- Yes. CVE-2026-29131 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-18142.
- When was CVE-2026-29131 published?
- CVE-2026-29131 was published on 2026-04-02 and last updated on 2026-06-17.
References
Affected products (1)
- cpe:2.3:a:seppmail:secure_email_gateway:*:*:*:*:*:*:*:*
More vulnerabilities in Seppmail Secure Email Gateway
- CVE-2026-29139 — Critical (CVSS 9.8): SEPPmail Secure Email Gateway before version 15.0.3 allows account takeover by abusing GINA account initialization to…
- CVE-2026-29143 — Critical (CVSS 9.1): SEPPmail Secure Email Gateway before version 15.0.3 does not properly authenticate the inner message of…
- CVE-2026-29133 — Critical (CVSS 9.1): SEPPmail Secure Email Gateway before version 15.0.3 allows an attacker to upload PGP keys with UIDs that do not match…
- CVE-2026-29138 — High (CVSS 7.5): SEPPmail Secure Email Gateway before version 15.0.3 allows attackers with a specially crafted email address to claim…
- CVE-2026-29135 — High (CVSS 7.5): SEPPmail Secure Email Gateway before version 15.0.3 allows an attacker to craft a password-tag that bypasses subject…
- CVE-2026-29134 — High (CVSS 7.5): SEPPmail Secure Email Gateway before version 15.0.3 allows an external user to modify GINA webdomain metadata and…
All CVEs affecting Seppmail Secure Email Gateway →
Other CWE-90 (LDAP Injection) vulnerabilities
- CVE-2026-44930 — Critical (CVSS 9.8): An LDAP injection vulnerability in the LDAP Certificate repository of the XKMS server in Apache CXF may allow an…
- CVE-2026-25560 — Critical (CVSS 9.8): WeKan versions prior to 8.19 contain an LDAP filter injection vulnerability in LDAP authentication. User-supplied…
- CVE-2024-54852 — Critical (CVSS 9.8): When LDAP connection is activated in Teedy versions between 1.9 to 1.12, the username field of the login form is…
- CVE-2024-33868 — Critical (CVSS 9.8): An issue was discovered in linqi before 1.4.0.1 on Windows. There is LDAP injection.
- CVE-2011-4069 — Critical (CVSS 9.8): html/admin/login.php in PacketFence before 3.0.2 allows remote attackers to conduct LDAP injection attacks and…
- CVE-2017-14596 — Critical (CVSS 9.8): In Joomla! before 3.8.0, inadequate escaping in the LDAP authentication plugin can result in a disclosure of a username…