CVE-2026-45051: Open Access Management (OpenAM) is an access management solution
Affects openamSource GCVE Database
Not known to be exploited · CVSS 9.2 Critical · fixed in 16.1.1 : patch openam as a priority.
Data as of 7 Nov 2026, 23:24 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 52% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 16.1.1
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NExploitation 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 by implementing proper deserialization filtering. Until upgrade, restrict access to delegated administration, provisioning, directory access, and legacy REST self-registration features to trusted users only to prevent injection of malicious serialized data. Review and harden configurations to minimize exposure of the WebAuthn flow.
Description
Open Access Management (OpenAM) prior to version 16.1.1 contains a deserialization vulnerability in its WebAuthnAuthentication component. The vulnerability arises because a serialized AuthenticatorImpl object graph is loaded from a user attribute without an ObjectInputFilter, allowing potential execution of malicious code if an attacker can write controlled data to that attribute. Exploitation requires the WebAuthn flow to be reachable and prior ability to write to the attribute via delegated administration or other means. This issue is fixed in version 16.1.1.