Public mode

No access to your tenant or devices. Every item links to its source. What this means

CVE-2026-79300

sesam · Vulnerability

CVSS 3.1 3.5 LOWCheck source for fixed versionsKEV status unknown

Original advisory

cve-program · CVE-2026-79300

Published

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.

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2026-79300

Published

sesam

Vendor product

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "defaultStatus": "unaffected",
                    "platforms": [
                        "Windows",
                        "Linux",
                        "x86",
                        "ARM",
                        "64 bit"
                    ],
                    "product": "sesam",
                    "vendor": "SEP",
                    "versions": [
                        {
                            "lessThan": "5.2.0.24",
                            "status": "affected",
                            "version": "1.0",
                            "versionType": "custom"
                        }
                    ]
                }

Original source record · Cite this exact observation · Complete original publisher JSON