CVE-2026-123545 · Other
NO FIX YET · SEE WHAT TO DO
OpenAM's OAuth 2.0 device authorization flow can be abused through cross-site request forgery when consent is skipped for implied-consent clients. A lured logged-in user can have an attacker's device code approved, giving the attacker access and ID tokens to call APIs as that user.
first public Oct 22, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
OpenAM deployments from 14.5.1 before 16.1.4 that use the OAuth 2.0 device authorization flow with implied-consent clients are exposed. Deployments on other versions, or without the device flow and implied-consent clients, are less exposed. The sources do not say whether managed or hosted OpenAM instances are patched by their operators.
Not affected if no-device-flow, no-implied-consent-clients, outside-affected-versions
Who cares identity, oauth, openam, self-hosted
16.1.4 or later, per the product range in the advisory.OpenAM from 14.5.1 before 16.1.4 contains a cross-site request forgery vulnerability in the OAuth 2.0 device authorization flow that allows attackers to approve device codes when consent is skipped for implied-consent clients. Attackers can start a device authorization and lure a logged-in user to a crafted page, obtaining access and ID tokens to call APIs as that user.
This page as .md · .json · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.