Advisory record · GHSA-4v2w-2wqp-mc85

OpenAM OAuth Authorization Bypass via PKCE Challenge

CVSS 9.1 CriticalCriticalEPSS 0.0053 · 45th percentile

Critical, because:

  • CVSS score 9.1: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 29 Jun 2026, 17:46 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.openidentityplatform.openam:openam-oauth2Maven<16.1.116.1.1
Identifiers
GHSA-4v2w-2wqp-mc85 · CVE-2026-48717
Weakness (CWE)
CWE-285
Published
29 Jun 2026
Updated
29 Jun 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

OpenAM (org.openidentityplatform.openam:openam-oauth2) versions before 16.1.1 let a PKCE-protected authorization code be redeemed without a code_verifier, because the token endpoint skips PKCE checks when the parameter is omitted and the codeVerifierEnforced setting is off by default. An attacker who intercepts an authorization code can obtain tokens without the verifier, and confidential clients also require client authentication material or a context that can redeem the code. Upgrade to version 16.1.1. Enabling the codeVerifierEnforced setting is a workaround you can apply yourself.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
9.1 Critical 4.0 CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0053, the 45th percentile, on 8 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:20 UTC First seen by agentprime
  2. 31 Oct 2026, 14:20 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.