org.openidentityplatform.openam:openam-oauth2

CVE-2026-44203

CVE-2026-44203 is a critical-severity cross-site scripting (XSS) vulnerability in org.openidentityplatform.openam:openam-oauth2 (maven), affecting versions >= 13.0.0, < 16.1.1. It is fixed in 16.1.1.

Key facts
CVSS score
9.3
Critical
Attack vector
Network
Issuing authority
GitHub Advisory Database
Affected package
org.openidentityplatform.openam:openam-oauth2
Fixed in
16.1.1
Disclosed
2026

Summary

Summary The OAuth 2.0 / OpenID Connect authorization endpoint does not sufficiently sanitize certain user-supplied parameters before incorporating them into the HTML response generated for the form_post response mode. This may allow an attacker to inject content into the rendered page in the context of the OpenAM origin.

Impact

What is cross-site scripting (XSS)?

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

Severity and exposure

CVE-2026-44203 has a CVSS score of 9.3 (Critical). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment.

A fixed version is available (16.1.1). Upgrading removes the vulnerable code path.

Affected versions

maven

  • org.openidentityplatform.openam:openam-oauth2 (>= 13.0.0, < 16.1.1)

Security releases

  • org.openidentityplatform.openam:openam-oauth2 → 16.1.1 (maven)
Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.

Kodem's runtime-powered SCA identifies whether CVE-2026-44203 is reachable in your applications. Explore open-source security for your team.

See if CVE-2026-44203 is reachable in your applications. Get a demo

Already deployed Kodem? See CVE-2026-44203 in your environment

Remediation advice

Upgrade org.openidentityplatform.openam:openam-oauth2 to 16.1.1 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently asked questions about CVE-2026-44203

What is CVE-2026-44203?

CVE-2026-44203 is a critical-severity cross-site scripting (XSS) vulnerability in org.openidentityplatform.openam:openam-oauth2 (maven), affecting versions >= 13.0.0, < 16.1.1. It is fixed in 16.1.1. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.

How severe is CVE-2026-44203?

CVE-2026-44203 has a CVSS score of 9.3 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of org.openidentityplatform.openam:openam-oauth2 are affected by CVE-2026-44203?

org.openidentityplatform.openam:openam-oauth2 (maven) versions >= 13.0.0, < 16.1.1 is affected.

Is there a fix for CVE-2026-44203?

Yes. CVE-2026-44203 is fixed in 16.1.1. Upgrade to this version or later.

Is CVE-2026-44203 exploitable, and should I be worried?

Whether CVE-2026-44203 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo

What actually determines whether CVE-2026-44203 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2026-44203?

Upgrade org.openidentityplatform.openam:openam-oauth2 to 16.1.1 or later.

Stop the waste.
Protect your environment with Kodem.