# CVE-2025-20628: Insufficient granularity of access control for Remote Connector Servers in client mode

> Attackers can spoof client-mode Remote Connector Servers to intercept or modify identity security properties like passwords and recovery info.

- **Severity:** Medium 6.9 (`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/E:U/S:P/AU:Y/R:U/V:C/RE:M/U:Red`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Apr 2026
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-wgxh-fmm3-r6v6

## What is CVE-2025-20628?

CVE-2025-20628 is a medium-severity missing authorization vulnerability in PingIDM, published on 7 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-1220 (Insufficient Granularity of Access Control)

## Which versions are affected by CVE-2025-20628?


## How do I fix CVE-2025-20628?

No fix has been published for CVE-2025-20628 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-20628 being exploited?

There is no known exploitation of CVE-2025-20628 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-20628 and fix it if it is affected.

What it is: CVE-2025-20628 is a medium-severity missing authorization vulnerability in PingIDM, published on 7 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-20628 in the wild and no public exploit code.

Affected product: PingIDM. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-20628/ (Markdown: https://insights.sbomify.com/CVE-2025-20628/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-20628
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-20628
- OSV: https://osv.dev/vulnerability/CVE-2025-20628

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-20628/
Summaries are generated and may contain mistakes; the official description above is the record.