---
id: "CVE-2026-123545"
page: "https://infrastack.ai/live/CVE-2026-123545"
kind: "vulnerability"
aliases: ["CVE-2026-123545"]
title: "OpenAM: cross-site request forgery in OAuth device flow exposes user tokens"
severity: "high"
cvss: 7.1
epss: null
exploited: false
status: "open"
category: "other"
products: []
ecosystems: []
tags: ["identity", "oauth", "openam", "other", "self-hosted"]
not_affected_if: ["no-device-flow", "no-implied-consent-clients", "outside-affected-versions"]
published_at: "2026-11-08T02:16:45+00:00"
first_seen_at: "2026-11-08T02:21:10+00:00"
updated_at: "2026-11-08T02:23:26+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-123545", "first_seen_at": "2026-11-08T02:21:10+00:00"}]
exploit_sources: []
---

# OpenAM: cross-site request forgery in OAuth device flow exposes user tokens

Link for people: https://infrastack.ai/live/CVE-2026-123545 (this .md is for agents)

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.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed OpenAM version, e.g. the version shown in the admin console, and compare it with the affected range 14.5.1 to before 16.1.4.
- Check whether the OAuth 2.0 device authorization grant is enabled and whether any clients use implied consent, per the vendor advisory.

## Fix

- OpenAM: move to `16.1.4` or later, per the product range in the advisory.

## Timeline

- 2026-11-08T02:21:10+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-123545

## Documents

- [advisory] Vendor advisory: github.com https://github.com/OpenIdentityPlatform/OpenAM/security/advisories/GHSA-545c-rm35-2jj2
- [advisory] Third-party advisory: www.vulncheck.com https://www.vulncheck.com/advisories/openam-14.5.1-before-16.1.4-csrf-in-oauth-2.0-device-flow

## From the sources

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.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_