CVE-2026-29131 | SEPPmail Secure Email Gateway up to 15.0.2 ldap injection
VulDBArchived Apr 02, 2026✓ Full text saved
A vulnerability categorized as problematic has been discovered in SEPPmail Secure Email Gateway up to 15.0.2 . Affected by this vulnerability is an unknown functionality of the component Email Handler . Executing a manipulation can lead to ldap injection. This vulnerability appears as CVE-2026-29131 . The attack may be performed from remote. There is no available exploit. It is advisable to upgrade the affected component.
Full text archived locally
✦ AI Summary· Claude Sonnet
VDB-354839 · CVE-2026-29131 · GCVE-0-2026-29131
SEPPMAIL SECURE EMAIL GATEWAY UP TO 15.0.2 LDAP INJECTION
HISTORYDIFFRELATEJSONXMLCTI
CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score
4.1 $0-$5k 1.18+
Summaryinfo
A vulnerability identified as problematic has been detected in SEPPmail Secure Email Gateway up to 15.0.2. Affected by this issue is some unknown functionality of the component Email Handler. The manipulation leads to ldap injection. This vulnerability is traded as CVE-2026-29131. It is possible to initiate the attack remotely. There is no exploit available. You should upgrade the affected component.
Detailsinfo
A vulnerability was found in SEPPmail Secure Email Gateway up to 15.0.2 and classified as problematic. This issue affects some unknown functionality of the component Email Handler. The manipulation with an unknown input leads to a ldap injection vulnerability. Using CWE to declare the problem leads to CWE-90. The product constructs all or part of an LDAP query using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended LDAP query when it is sent to a downstream component. Impacted is confidentiality. The summary by CVE is:
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.
The weakness was shared by Andris Suter-Dörig. It is possible to read the advisory at downloads.seppmail.com. The identification of this vulnerability is CVE-2026-29131 since 03/04/2026. The exploitation is known to be easy. The attack may be initiated remotely. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1505 according to MITRE ATT&CK.
Upgrading to version 15.0.3 eliminates this vulnerability.
Productinfo
Vendor
SEPPmail
Name
Secure Email Gateway
Version
15.0.0
15.0.1
15.0.2
CPE 2.3info
🔒
🔒
🔒
CPE 2.2info
🔒
🔒
🔒
CVSSv4info
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3info
VulDB Meta Base Score: 4.3
VulDB Meta Temp Score: 4.1
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2info
Vector Complexity Authentication Confidentiality Integrity Availability
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploitinginfo
Class: Ldap injection
CWE: CWE-90 / CWE-74 / CWE-707
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
0-Day Unlock Unlock Unlock Unlock
Today Unlock Unlock Unlock Unlock
Threat Intelligenceinfo
Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
Countermeasuresinfo
Recommended: Upgrade
Status: 🔍
0-Day Time: 🔒
Upgrade: Secure Email Gateway 15.0.3
Timelineinfo
03/04/2026 CVE reserved
04/02/2026 +28 days Advisory disclosed
04/02/2026 +0 days VulDB entry created
04/02/2026 +0 days VulDB entry last update
Sourcesinfo
Advisory: downloads.seppmail.com
Researcher: Andris Suter-Dörig
Status: Confirmed
CVE: CVE-2026-29131 (🔒)
GCVE (CVE): GCVE-0-2026-29131
GCVE (VulDB): GCVE-100-354839
Entryinfo
Created: 04/02/2026 11:21
Changes: 04/02/2026 11:21 (67)
Complete: 🔍
Cache ID: 99:F4C:101
Discussion
No comments yet. Languages: en.
Please log in to comment.
◂ PreviousOverviewNext ▸