CVE-2026-79300

LOWPre-NVD 3.53.5—
EchelonGraph scoreHIGH confidence

Score 3.5 from GitHub Security Advisory (severity: LOW) published 2026-09-13. a secondary CVSS source baseline 3.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
3.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 3.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
3.5
EG Score
3.5(high)
EG Risk
16(Track)
EG Risk 16/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity35% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
12%
KEV
Not listed

Published

September 12, 2026

Last Modified

September 14, 2026

References (1)

Vendor Advisories for CVE-2026-79300(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 14× in last 7d / 14× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-17 10:57 UTCEG score recompute
  3. 2026-09-17 10:57 UTCGHSA enrichment
  4. 2026-09-16 14:08 UTCEPSS rescore
  5. 2026-09-16 05:15 UTCEPSS rescore
  6. 2026-09-15 03:12 UTCEPSS rescore
  7. 2026-09-15 03:12 UTCEPSS rescore
  8. 2026-09-14 17:28 UTCEG score recompute
  9. 2026-09-14 17:28 UTCGHSA enrichment
  10. 2026-09-14 16:36 UTCEG score recompute
  11. 2026-09-14 16:35 UTCGHSA enrichment
  12. 2026-09-12 23:18 UTCEG score recompute
  13. 2026-09-12 22:27 UTCEG score recompute
  14. 2026-09-12 22:27 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-79300?
CVE-2026-79300 is a low vulnerability published on September 12, 2026. 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…
When was CVE-2026-79300 disclosed?
CVE-2026-79300 was first published in the National Vulnerability Database on September 12, 2026, with the most recent update on September 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-79300 actively exploited?
CVE-2026-79300 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 88.2% of all scored CVEs.
What is the CVSS score of CVE-2026-79300?
CVE-2026-79300 has a CVSS v3 base score of 3.5 (NVD).
How do I remediate CVE-2026-79300?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-79300, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-79300

Explore →

Is Your Infrastructure Affected by CVE-2026-79300?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs