CVE-2026-115546EUVD-2026-108568GHSA-PQRR-J665-PF8M
Authentication Source Verification Issue in Okta Access Gateway
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 2026.10.2
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
Okta Access Gateway is affected by an authentication source verification flaw that lets a user who already has an active session change the authentication source during sign-on. This could allow that user to obtain a SAML assertion that grants access to the Admin Console.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
Okta Access Gateway (OAG) does not validate the selected authentication source during sign-on. An authenticated user with an active session can modify the authentication source parameter, which may generate a SAML assertion granting access to the Admin Console.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Okta Okta Access Gateway
fixed in 2026.10.2