CVE-2026-79300: Software Security Vulnerability Vulnerability

LOW
Advisory Identifier: GHSA-7gr9-32jg-84c9
Share
CVSS 3.5
CWE-180
Published
Advisory Summary

CVE-2026-79300 is a LOW (CVSS 3.5) security vulnerability vulnerability (CWE-180: Incorrect Behavior Order: Validate Before Canonicalize) affecting Software libraries in the Maven ecosystem. The weakness occurs when the product validates input before it is canonicalized, which prevents the product from detecting data that becomes invalid after the canonicalization step.. Remediation is available in the latest vendor maintenance releases.

CVE-2026-79300 at a Glance

CVE Identifier CVE-2026-79300
GHSA Identifier GHSA-7gr9-32jg-84c9
Severity LOW
CVSS v3.1 Base Score 3.5
CWE Classification CWE-180: Incorrect Behavior Order: Validate Before Canonicalize
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 3.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:L/A:N).

Attack Vector Network (AV:N)
Attack Complexity High (AC:H)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Changed (S:C)
Confidentiality None (C:N)
Integrity Low (I:L)
Availability None (A:N)

How to Fix CVE-2026-79300

To remediate this vulnerability, upgrade all affected Software dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

mvn dependency:tree

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2026-79300, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree

Analyze the terminal output to locate any version of Software in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: The mvn dependency:tree command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-180: Incorrect Behavior Order: Validate Before Canonicalize, where the product validates input before it is canonicalized, which prevents the product from detecting data that becomes invalid after the canonicalization step. In Software, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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.

References

NVD — CVE-2026-79300 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-79300
wiki.sep.de/wiki/index.php/rele... WEB
https://wiki.sep.de/wiki/index.php/Release_Notes_5.2.0_Artemis#fixed

Frequently Asked Questions

What is CVE-2026-79300?
CVE-2026-79300 is a security vulnerability in Software classified as a security vulnerability vulnerability under CWE-180: Incorrect Behavior Order: Validate Before Canonicalize.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-79300?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What is the CVSS score of CVE-2026-79300?
CVE-2026-79300 has a CVSS v3.1 base score of 3.5 (LOW) with vector string CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:L/A:N.
What CWE is associated with CVE-2026-79300?
CVE-2026-79300 is classified under CWE-180: Incorrect Behavior Order: Validate Before Canonicalize (The product validates input before it is canonicalized, which prevents the product from detecting data that becomes invalid after the canonicalization step.).
How can I check Maven dependencies for CVE-2026-79300?
Run the dependency tree command: 'mvn dependency:tree'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-7gr9-32jg-84c9",
  "modified" : "2026-09-13T00:31:19Z",
  "published" : "2026-09-13T00:31:19Z",
  "aliases" : [ "CVE-2026-79300" ],
  "details" : "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.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:L/A:N"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-79300"
  }, {
    "type" : "WEB",
    "url" : "https://wiki.sep.de/wiki/index.php/Release_Notes_5.2.0_Artemis#fixed"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-180" ],
    "severity" : "LOW",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-12T23:17:00Z"
  }
}