Track vulnerabilities like this one. Sign up free to get alerted when software you use is affected.
6.2

CVE-2026-44202: OpenAM lets logged-in users trigger external requests

CVE-2026-44202 · published 4 months ago
Summary

The OpenAM identity platform’s session management endpoint accepts URLs from authenticated users without proper checks. An attacker who is already logged in can cause the server to contact any address they choose, potentially leaking session information. Apply the vendor’s update or restrict the endpoint to trusted URLs to stop this behavior.

What to do
  • Update openidentityplatform org.openidentityplatform.openam:openam-core to version 16.1.1.
  • Update org.openidentityplatform.openam:openam-core to version 16.1.1.
Affected software
Ecosystem VendorProductAffected versions
– openidentityplatform openam < 16.1.1
maven openidentityplatform org.openidentityplatform.openam:openam-core <= 16.0.6
Fix: upgrade to 16.1.1
Maven openidentityplatform org.openidentityplatform.openam:openam-core < 16.1.1
Fix: upgrade to 16.1.1
Ubuntu:16.04:LTS canonical openam All versions
maven – org.openidentityplatform.openam:openam-core <= 16.0.6
Fix: upgrade to 16.1.1
Maven – org.openidentityplatform.openam:openam-core < 16.1.1
Fix: upgrade to 16.1.1
Original advisory text
OpenAM Authenticated Server-Side Request Forgery (SSRF) via `/sessionservice`
OpenAM (Open Identity Platform) is an open-source Identity and Access Management (IAM) platform derived from ForgeRock OpenAM, providing SSO, OAuth2, SAML, and OpenID Connect capabilities. It is widely deployed in enterprise environments as a central authentication gateway.

The `/sessionservice` endpoint, used for internal session management operations, does not sufficiently restrict the URLs that authenticated users may register for session event notifications. Under certain conditions, this may result in outbound server-side requests to attacker-controlled destinations, potentially exposing session-related data.

This behavior results in a **server-side request forgery (SSRF)** vulnerability, where an authenticated attacker can trigger outbound requests to arbitrary destinations.

## Credit

Discovered by **JD-Security SHENYI Team**
Fix within
Internet-facing 60 days
Internal At next upgrade
  • Not known to be exploited
  • Needs hands-on effort to exploit
  • Gives an attacker partial control
Severity
6.2 Medium
Exploitation
<1% chance of attack within 30 days
Type
CWE-918Server-Side Request Forgery (SSRF)
Timeline
Published22 Jun 2026
Updated4 Nov 2026
First seen22 Jun 2026
Track software like this
Free during beta