CVE-2026-79300
- State
- Published
- Severity
- 3.5 Low
- Published
- Sep 12, 2026
- Updated
- Sep 14, 2026
- Reserved
- Aug 25, 2026
Description
SEP sesam before 5.2.0.24 mishandles User Authorization with MFA. If AD authentication is configured and MFA is enforced, an attacker can create a second OTP access capability. SEP sesam and Active Directory handle username capitalization differently, which may allow multiple SEP sesam user accounts to be created for the same Active Directory (AD) account. Active Directory treats usernames as case-insensitive, while SEP sesam distinguishes between different letter casing. As a result, the same AD user can be represented by multiple SEP sesam user accounts that differ only in username capitalization. When Active Directory authentication is configured and multi-factor authentication (MFA) is enforced, this behavior may allow an additional OTP Authenticator to be registered for the same AD account, reducing the effectiveness of MFA protection.
Scores
| CVSS | Score | Vector | Source |
|---|---|---|---|
| 3.1 | 3.5 Low | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:L/A:N | mitre |
Weaknesses
- CWE-180 Incorrect Behavior Order: Validate Before Canonicalize
Affected Products
| Product | Versions |
|---|---|
sesamSEP |
|
References
- https://wiki.sep.de/wiki/index.php/Release_Notes_5.2.0_Artemis#fixedrelease-notesvendor-advisory
Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.