# CVE-2026-79300 — SEP sesam

> As of 2026-09-12, CVE-2026-79300 is a LOW-severity vulnerability in SEP sesam, CVSS v3.1 3.5. No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-79300 as of 2026-09-12; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

**Last updated:** 2026-09-12

## What is CVE-2026-79300?

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.

The record classifies CVE-2026-79300 under weakness class [CWE-180](https://cwe.mitre.org/data/definitions/180.html). Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs low-privilege credentials, needs no user interaction. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 23 days ago.

## Severity and exploitation probability

- **CVSS v3.1 base score:** 3.5 — LOW (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:L/A:N`)
- **CISA KEV:** Not listed in the CISA Known Exploited Vulnerabilities catalog
- **Threadlinqs priority:** 1.8/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- **Published:** 2026-09-12

## Is CVE-2026-79300 being exploited?

It currently carries a trending score of 30 in the Threadlinqs vulnerability feed.

## Affected products and versions

- **SEP**: sesam

## How to fix CVE-2026-79300

No vendor patch reference has been recorded for CVE-2026-79300 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

## Threat activity tracking CVE-2026-79300

No threat campaign in the Threadlinqs corpus currently references CVE-2026-79300, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

## Sources

Enriched from CVE.org, NVD. Last verified by Threadlinqs on 2026-09-14. This product uses the NVD API but is not endorsed or certified by the NVD.

**Vendor advisory and patch**

- [wiki.sep.de — release notes](https://wiki.sep.de/wiki/index.php/Release_Notes_5.2.0_Artemis#fixed)

Canonical: https://intel.threadlinqs.com/cve/CVE-2026-79300
Full detection coverage and IOCs for threats exploiting CVE-2026-79300 via the Threadlinqs MCP server (Purple tier): https://intel.threadlinqs.com/mcp