{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-79300 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-79300 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-79300 is a low-severity authentication bypass vulnerability in SEP sesam, published on 12 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-79300 and fix it if it is affected.\n\nWhat it is: CVE-2026-79300 is a low-severity authentication bypass vulnerability in SEP sesam, published on 12 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-79300 in the wild and no public exploit code.\n\nAffected product: SEP sesam. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-79300/ (Markdown: https://insights.sbomify.com/CVE-2026-79300/index.md)","id":"CVE-2026-79300","markdown":"https://insights.sbomify.com/CVE-2026-79300/index.md","name":"CVE-2026-79300","record":{"aliases":["GHSA-7gr9-32jg-84c9"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"SEP sesam backup software","requires_auth":"low_privilege","summary":"Attackers can bypass MFA by creating duplicate user accounts with different capitalization in SEP sesam when using Active Directory authentication.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":3.5,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-180","name":"Incorrect Behavior Order: Validate Before Canonicalize"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Auth bypass in sesam","id":"CVE-2026-79300","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"SQL injection in n/a","id":"CVE-2026-79303"},"packages":[],"prev":{"headline":"Code injection in n/a","id":"CVE-2026-79298"},"products":["sesam"],"published":"2026-09-12","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-14","vendors":["SEP"]},"summary":"Attackers can bypass MFA by creating duplicate user accounts with different capitalization in SEP sesam when using Active Directory authentication.","url":"https://insights.sbomify.com/CVE-2026-79300/"}