# CVE-2025-21085: PingFederate OAuth Grant attribute duplication may use excessive memory

> Attackers can cause excessive memory utilization in PingFederate via OAuth2 grant duplication, leading to denial of service.

- **Severity:** Low 2.1 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:N/VI:N/VA:L/SC:N/SI:N/SA:L/S:P/AU:Y/R:A/RE:L/U:Amber`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 Jun 2025
- **Updated:** 16 Jun 2025
- **Also known as:** GHSA-4755-93r4-qvxj

## What is CVE-2025-21085?

CVE-2025-21085 is a low-severity denial of service vulnerability in PingFederate, published on 15 Jun 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

PingFederate OAuth2 grant duplication in PostgreSQL persistent storage allows OAuth2 requests to use excessive memory utilization.

Weakness: CWE-462 (Duplicate Key in Associative List (Alist))

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


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

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

## Is CVE-2025-21085 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-21085 is a low-severity denial of service vulnerability in PingFederate, published on 15 Jun 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-21085 in the wild and no public exploit code.

Affected product: PingFederate. 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-21085/ (Markdown: https://insights.sbomify.com/CVE-2025-21085/index.md)
```

## Sources

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

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