Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate with valid OAG session
-
DeliveryModify authentication source parameter
-
ExploitBypass authentication-source validation
-
ExecutionOAG issues SAML assertion
-
ImpactGain Okta Access Gateway Admin Console access
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Object-level authorization, IDOR prevention
|
| Exploitation Conditions | Exploitation requires the attacker to already be an authenticated OAG user with an active session; the attacker then alters the authentication-source parameter during sign-on, which OAG fails to validate, producing a SAML assertion that grants Admin Console access. Limiting factors: valid credentials / an active session are mandatory (this is privilege escalation, not unauthenticated access), the target product is specifically Okta Access Gateway (per CPE cpe:2.3:a:okta:okta_access_gateway), and the vendor's CVSS AC:H indicates the parameter manipulation is not trivial to perform reliably. No special non-default configuration or user interaction is described as required beyond possessing an authenticated session. |
| Impact | This is a credible privilege-escalation issue that warrants prompt attention but is not an emergency. The vendor-assigned CVSS of 8.1 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H) reflects network reach and full confidentiality/integrity/availability impact via unauthorized Admin Console access, tempered by high attack complexity. A key internal conflict must be flagged: the CVSS vector states PR:N (no privileges required), yet the description explicitly requires 'an authenticated user with an active session' who modifies the authentication source parameter - this is an authenticated privilege-escalation flaw, not an unauthenticated bypass, so PR:N appears incorrect and authentication requirements should be read from the description, not the vector. CWE-639 (authorization bypass through a user-controlled key) matches the described mechanism: the authentication source is user-modifiable and not server-validated. No EPSS score, no CISA KEV listing, and no public PoC or exploit reference were provided, so there is no evidence of active or at-scale exploitation; the vuln.today decision label is 'this_week', consistent with a serious-but-not-actively-exploited item. The real priority is elevated because the outcome is Admin Console (administrative) access and the reporter is the vendor itself, but the authenticated precondition plus AC:H meaningfully constrain opportunistic mass exploitation. Patch availability and fixed versions are not stated in the supplied data and must be confirmed via the Okta advisory. |
| Exploit ScenarioDerived | An attacker who already holds a valid OAG user account (for example a low-privilege employee or a compromised standard credential) establishes an active session, then tampers with the authentication-source parameter during sign-on. Because OAG does not validate the selected authentication source, the manipulated request yields a SAML assertion that grants access to the Admin Console, escalating the attacker from ordinary user to administrator. No public exploit identified at time of analysis; the high attack complexity implies the precise parameter manipulation is non-trivial. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 23, 2026
Privilege escalation in Okta Access Gateway allows an already authenticated user with an active session to obtain Admin Console access by altering the authentication-source parameter during sign-on, which OAG fails to validate before issuing a SAML assertion. Okta rates the flaw 8.1 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H), while our assessment adjusts the privilege requirement to PR:L because valid credentials and a live session are mandatory; the AC:H metric reflects that the parameter manipulation is not trivial to perform reliably. No public exploit code has been identified at time of analysis and the issue is not in CISA KEV, but successful abuse grants administrative control of the gateway, so it warrants prompt patching on this week's cycle rather than emergency action.
RemediationAI
No vendor-released patch was identified in the available data for CVE-2026-115546, so the first step is to pull the Okta security advisory at http://trust.okta.com/security-advisories/authentication-source-verification-issue-in-okta-access-gateway-cve-2026-115546 and apply the fixed release Okta lists for each deployed branch; because the CPE is a wildcard, confirm the exact version mapping rather than assuming a given build is unaffected. Until that fix is in place, reduce exposure by restricting network reachability of the OAG Admin Console to a management network or jump host so that an assertion minted through the tampered sign-on flow cannot be used from an untrusted segment (trade-off: administrators lose direct access and must route through the restricted path), and by reviewing which accounts are permitted to hold concurrent OAG sessions, since exploitation requires an active authenticated session (trade-off: tighter session policy adds friction for legitimate federated users). Monitor sign-on telemetry and gateway logs for authentication-source parameters that differ from the source bound to the session's originating identity provider, and alert on Admin Console authentications that follow such a change, as this is the observable signature of the bypass. Rotating credentials and terminating existing sessions limits an attacker who has already obtained a session, but does not address the underlying validation gap.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Okta Access Gateway is an on-premises reverse-proxy and identity-bridging component that fronts internal applications and brokers sign-on by selecting an authentication source (typically an identity provider) and then minting a SAML assertion for the downstream resource. The flaw is a CWE-639 authorization bypass through a user-controlled key: the authentication-source selector is taken from the request rather than being bound to the value established for the user's authenticated session, so the trust decision is made on data the client can rewrite. In this case the resulting assertion is accepted for the Admin Console rather than for an ordinary application, which converts a session-level manipulation into administrative access. The CPE entry cpe:2.3:a:okta:okta_access_gateway:*:*:*:*:*:*:*:* uses a wildcard version, so the advisory reference does not pin the defect to a specific release branch in the supplied data; the affected version range and the exact request flow, including which endpoint or parameter name is involved, are not described in the available sources and should be confirmed against Okta's security advisory. No non-default configuration prerequisite is documented, beyond the attacker holding an authenticated session.
Know when Okta Access Gateway gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Description requires an authenticated active session so PR:L not PR:N; network-reachable sign-on flow (AV:N), non-trivial parameter manipulation (AC:H), and Admin Console takeover yields full C:H/I:H/A:H.
Primary rating from Vendor (Okta).
CVSS VectorVendor: Okta
Lifecycle Timeline
2DescriptionCVE.org
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.
Executive ViewAI
Okta Access Gateway (OAG) contains a high-severity privilege escalation flaw that allows any authenticated user with an active session to gain administrative control of the gateway by manipulating the authentication-source parameter during sign-on. This puts the organization's access management infrastructure at risk of unauthorized administrative access, potentially compromising all downstream applications and sensitive data protected by OAG. Leadership should prioritize remediation as part of this week's security cycle due to the high business impact of breached gateway administration.
No vendor-released patch identified at time of analysis. Interim mitigations include restricting network access to the OAG admin console to trusted IPs, enforcing strict session management, monitoring authentication logs for anomalies, and applying Okta's recommended configuration hardening until a patch is available.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
EUVD-2026-108568
GHSA-pqrr-j665-pf8m
NVD
CVE.org
Exploit-DB