Ping Identity PingDirectory up to 9.3.0.8/10.1.0.5/10.2.0.5/10.3.0.3 memory leak
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 2.6 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in Ping Identity PingDirectory up to 9.3.0.8/10.1.0.5/10.2.0.5/10.3.0.3. This affects an unknown function. Performing a manipulation results in memory leak. This vulnerability is identified as CVE-2026-20746. The attack can be initiated remotely. There is not any exploit available. It is suggested to upgrade the affected component.
Details
A vulnerability classified as problematic has been found in Ping Identity PingDirectory up to 9.3.0.8/10.1.0.5/10.2.0.5/10.3.0.3. This affects an unknown code. The manipulation with an unknown input leads to a memory leak vulnerability. CWE is classifying the issue as CWE-401. The product does not sufficiently track and release allocated memory after it has been used, which slowly consumes remaining memory. This is going to have an impact on availability. The summary by CVE is:
Virtual attribute handling in Ping Identity PingDirectory in affected versions allows only authorized users to exhaust java memory heap when recent login history is enabled and copying virtual attributes that reference ds-privilege-name values.
The advisory is shared at docs.pingidentity.com. This vulnerability is uniquely identified as CVE-2026-20746 since 01/07/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. The exploitation needs additional levels of successful authentication. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1499 for this issue.
Upgrading to version 11.0.0.1 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
- 9.3.0.0
- 9.3.0.1
- 9.3.0.2
- 9.3.0.3
- 9.3.0.4
- 9.3.0.5
- 9.3.0.6
- 9.3.0.7
- 9.3.0.8
- 10.1.0.0
- 10.1.0.1
- 10.1.0.2
- 10.1.0.3
- 10.1.0.4
- 10.1.0.5
- 10.2.0.0
- 10.2.0.1
- 10.2.0.2
- 10.2.0.3
- 10.2.0.4
- 10.2.0.5
- 10.3.0.0
- 10.3.0.1
- 10.3.0.2
- 10.3.0.3
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 2.7VulDB Meta Temp Score: 2.6
VulDB Base Score: 2.7
VulDB Temp Score: 2.6
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Memory leakCWE: CWE-401 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: PingDirectory 11.0.0.1
Timeline
01/07/2026 CVE reserved06/12/2026 Advisory disclosed
06/12/2026 VulDB entry created
06/12/2026 VulDB entry last update
Sources
Advisory: docs.pingidentity.comStatus: Confirmed
CVE: CVE-2026-20746 (🔒)
GCVE (CVE): GCVE-0-2026-20746
GCVE (VulDB): GCVE-100-370521
Entry
Created: 06/12/2026 06:26Changes: 06/12/2026 06:26 (71)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.