CVE-2026-79300: Low severity SEP sesam SEP sesam vulnerability
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.
Affected Software
Remediation
Information
Event History
Frequently Asked Questions
Which deployments are exposed to this issue?
Deployments using Active Directory authentication in SEP sesam are affected when MFA is enforced. The issue relies on the differing treatment of username capitalization by Active Directory and SEP sesam.
What access does an attacker need to exploit it?
The attacker needs low-level privileges. Exploitation also requires creating SEP sesam user accounts for the same AD account using usernames that differ only by letter capitalization, then registering an additional OTP Authenticator.
Are versions with the fix available?
The issue is fixed in SEP sesam release versions 5.2.0.24 and later. Updating is strongly recommended where AD authentication is used.