CVE-2026-115546 Okta CVE debrief

Who should care

Okta Access Gateway administrators and security teams should assess exposure and prioritize verification of Okta Access Gateway versions and configurations. They should also ensure proper authentication source validation, monitor for suspicious Admin Console access, and review and update Okta Access Gateway settings to prevent unauthorized authentication source modifications. Additionally, operators, platforms, vulnerability-management, and security teams

Why it matters

The authentication source verification issue in Okta Access Gateway requires defenders to prioritize verification of Okta Access Gateway versions and configurations, ensure proper authentication source validation, and monitor for suspicious Admin Console access.

• Potential unauthorized access to the Admin Console
• Need to verify Okta Access Gateway versions and configurations
• Requirement to monitor for suspicious Admin Console access
• Necessity to review and update Okta Access Gateway settings

Technical summary

The Okta Access Gateway does not validate the selected authentication source during sign-on, allowing an authenticated user with an active session to modify the authentication source parameter and potentially generate a SAML assertion granting access to the Admin Console. This issue requires defenders to prioritize verifying Okta Access Gateway versions and configurations, ensuring proper authentication source validation, and monitoring for suspicious Admin Console access. The affected product context and defensive impact should be considered when assessing this vulnerability.

Defensive priority

Defenders should prioritize verifying Okta Access Gateway versions and configurations, ensuring proper authentication source validation, and monitoring for suspicious Admin Console access.

Recommended defensive actions

• Verify Okta Access Gateway versions and configurations to ensure proper authentication source validation
• Monitor for suspicious Admin Console access and implement additional logging and monitoring measures
• Review and update Okta Access Gateway settings to prevent unauthorized authentication source modifications
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
• Check relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

The CVE Program record and NVD vulnerability detail provide official information on the authentication source verification issue in Okta Access Gateway. The issue is based on the CVE Program record with source-provided CVE metadata and the official NIST NVD detail page and source-specific vulnerability assessment. The source item provides details on the authentication source verification issue in Okta Access Gateway. However, the details are limited, and defenders should verify the affected scope, severity, and vendor guidance.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.