/

CVE-2026-45048

Severity:

HIGH RISK

(8.5)

Broken Access Control (CWE-285) in OpenAM Sessions

CVE-2026-45048

Awaiting Analysis

Vulnerability type

Category:

Broken Access Control

CWE:

CWE-200, CWE-285

Impact:

Session Credential Disclosure and Account Takeover

Severity:

HIGH RISK

(8.5)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

OpenAM fails to verify that an authenticated user is authorized to view the session information they request when stateful session storage is enabled. A low-privileged user who knows another identity's identifier may obtain that user's active session credentials, potentially enabling session hijacking and account takeover.

Affected context

The issue occurs in OpenAM deployments before 16.1.1 that use stateful session storage and expose the affected session management endpoint. Risk is present when the endpoint accepts an authenticated request without adequately checking whether the requester owns the referenced identity or has sufficient administrative privileges.

Exploit preconditions

  • Attack surface: OpenAM session management endpoint
  • Required access: An authenticated account with relatively low privileges
  • Required knowledge: The target identity identifier must be known or discoverable
  • Trigger point: A session-information request for another identity
  • Why exploitation is possible: SessionRequestHandler does not consistently enforce ownership or privilege checks before returning session data

Why this happens

The underlying flaw is an authorization failure in session-information retrieval. The endpoint uses a user-supplied identity reference without reliably confirming that the requester owns the referenced account or has an administrative role. This maps primarily to CWE-285: Improper Authorization, with a related CWE-200: Exposure of Sensitive Information impact because session credentials may be disclosed to an unauthorized party.

Potential impact

  • An attacker may obtain another user's active session credentials
  • A compromised session could allow impersonation of the affected user
  • Accounts with elevated privileges could be targeted for administrative access
  • Unauthorized access could lead to data exposure or changes to protected resources
  • Session confidentiality and trust boundaries could be weakened across the deployment

General mitigation guidance

Mitigation generally centers on enforcing authorization at the session-information access boundary.

Common defensive patterns include:

  • Require explicit ownership checks before returning user-specific session data
  • Restrict session inspection to narrowly defined administrative roles
  • Apply deny-by-default authorization policies to identity-referenced endpoints
  • Avoid returning session credentials or other bearer secrets through diagnostic APIs
  • Minimize session data exposure and protect sensitive values in transit and at rest
  • Use short session lifetimes and revocation controls to reduce the impact of credential disclosure
  • Separate administrative session-management capabilities from ordinary authenticated access

How teams detect issues like this

Organizations can assess for this class of issue through:

  • Static analysis and code review rules that flag identity-based lookups without adjacent authorization checks
  • Review of endpoint handlers that accept account, subject, or identity identifiers from request input
  • Tests verifying that users cannot retrieve session data for unrelated identities
  • Authorization policy checks ensuring session inspection requires explicit administrative privileges
  • Audit-log monitoring for repeated session queries across many identities or unusual access by low-privileged accounts
  • Automated security testing that evaluates horizontal and vertical authorization boundaries using non-sensitive test sessions

Sources

SourceLink
github.comgithub.com/OpenIdentityPlatform/OpenAM/commit/f775b42236b3cb94e3a02a19f4a4f4f5cc0b91c4
github.comgithub.com/OpenIdentityPlatform/OpenAM/releases/tag/16.1.1
github.comgithub.com/OpenIdentityPlatform/OpenAM/security/advisories/GHSA-vvhj-w2jq-263q

Frequently asked

questions

It may be exploitable through the OpenAM session management endpoint when that endpoint is reachable by an authenticated user and stateful session storage is enabled. The exact exposure depends on deployment and network controls.

The attacker generally needs a valid authenticated account, knowledge of a target identity identifier, and network access to the affected endpoint. Administrative privileges should not be required when authorization checks are missing.

Enforce server-side ownership or role-based authorization before returning any session information, and avoid exposing bearer credentials through session-management responses.

Apply deny-by-default access policies, test horizontal and vertical authorization boundaries, minimize sensitive response data, and monitor identity-referenced session queries for anomalous behavior.

Find out what's already
exploitable in your codebase.