CVE-2026-45048: Open Access Management (OpenAM) is an access management solution
Affects openamSource GCVE Database
Not known to be exploited · CVSS 8.5 High · fixed in 16.1.1 : patch openam soon.
Data as of 8 Nov 2026, 23:24 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 37% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 16.1.1
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 15 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 8 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 16.04 LTSopenampkg:deb/ubuntu/openam?arch=source&distro=xenialOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade OpenAM to version 16.1.1 or later, where this vulnerability is fixed. No other mitigation is indicated by the vendor advisory.
Description
Open Access Management (OpenAM) versions prior to 16.1.1 contain a vulnerability in the SessionRequestHandler component of the session management endpoint. This flaw allows a low-privileged authenticated user to bypass ownership and privilege checks when querying session information in deployments using stateful session storage. An attacker who knows a target identity identifier can retrieve active session credentials of another user, including those of more privileged accounts, enabling session hijacking. The issue is resolved in version 16.1.1.