PingAM, PingIDM and PingGateway
CVE-2025-20628: Insufficient granularity of access control for Remote Connector Servers in client mode
An insufficient granularity of access control vulnerability exists in PingIDM (formerly ForgeRock Identity Management) where administrators cannot properly configure access rules for Remote Connector Servers (RCS) running in client mode.
Published
Automatic summary from the vendor's CVE record. We haven't written a full analysis of this vulnerability yet.
Affected and fixed versions
| Product / branch | Fixed in |
|---|---|
| PingIDM 7.5 | See the advisory |
| PingIDM 7.4.0 to 7.4.1 | Upgrade past 7.4.1; see the advisory |
| PingIDM 7.3.0 to 7.3.1 | Upgrade past 7.3.1; see the advisory |
| PingIDM 7.2.0 to 7.2.2 | Upgrade past 7.2.2; see the advisory |
| PingIDM 0 to 7.1.* | Upgrade past 7.1.*; see the advisory |
Always confirm against the vendor advisory, which lists every fixed hotfix.
What it is
An insufficient granularity of access control vulnerability exists in PingIDM (formerly ForgeRock Identity Management) where administrators cannot properly configure access rules for Remote Connector Servers (RCS) running in client mode. This means attackers can spoof a client-mode RCS (if one exists) to intercept and/or modify an identity’s security-relevant properties, such as passwords and account recovery information. This issue is exploitable only when an RCS is configured to run in client mode.
Am I affected?
At least one RCS configured in client mode in PingIDM
Workarounds
Configure a reverse proxy (such as PingGateway) to enforce IP and certificate-based rules to the /openicf endpoint.
Configure all RCS instances to run in server mode.
Sources
KEV status, EPSS score and vendor data refreshed automatically, last on 13 Oct 2026.