CVE-2025-20628Network attack vector

Identity data interception and modification via spoofed RCS

Published Apr 7, 2026 · Updated Apr 7, 2026

Access control failure in PingIDM allows remote attackers to spoof client-mode RCS connections through the /openicf endpoint. The endpoint lacks sufficiently granular access and authentication controls, so a spoofed RCS can be accepted as a configured client. Exploitation requires at least one RCS in client mode and permits interception or modification of passwords and account-recovery data.

CVSS severity6.9
Medium
EPSS probability0.24%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Access control failure in PingIDM allows remote attackers to spoof client-mode RCS connections through the /openicf endpoint. The endpoint lacks sufficiently granular access and authentication controls, so a spoofed RCS can be accepted as a configured client. Exploitation requires at least one RCS in client mode and permits interception or modification of passwords and account-recovery data.

The record

CVE
CVE-2025-20628
Published
Apr 7, 2026
Updated
Apr 7, 2026
Vendor
Ping Identity
Product
PingIDM
Classifications
CWE-1220, CAPEC-1, T1557
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Apr 7, 2026CVE publishedPublication date reported by the CVE source.
  2. Apr 7, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=0 <=7.1.*
  2. Affected versionversion=7.2.0 <=7.2.2
  3. Affected versionversion=7.3.0 <=7.3.1
  4. Affected versionversion=7.4.0 <=7.4.1
  5. Affected versionversion=7.5.0

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Ping Identity · PingIDMversion=0 <=7.1.*; version=7.2.0 <=7.2.2; version=7.3.0 <=7.3.1; version=7.4.0 <=7.4.1; version=7.5.0

Published CVSS scores

6.9Ping Identity CorporationCVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-1220Insufficient Granularity of Access Control
CAPEC-1Accessing Functionality Not Properly Constrained by ACLs
T1557Adversary-in-the-Middle

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo