# CVE-2025-26862: PingFederate unexpected browser flow initiation in redirectless mode

> Attackers can bypass security controls in non-default redirectless mode to render authentication forms, enabling brute force login attempts against PingFederate.

- **Severity:** Not scored
- **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:** 27 Oct 2025
- **Updated:** 27 Oct 2025
- **Also known as:** GHSA-h7m5-vjwp-2jfx

## What is CVE-2025-26862?

CVE-2025-26862 is a vulnerability in PingFederate, published on 27 Oct 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

Unexpected authentication form rendering in HTML Form Adapter using only non-default redirectless mode in PingFederate allows authentication attempts which may enable brute force login attacks.

Weakness: CWE-307 (Improper Restriction of Excessive Authentication Attempts)

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


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

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

## Is CVE-2025-26862 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-26862 is a vulnerability in PingFederate, published on 27 Oct 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-26862 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-26862/ (Markdown: https://insights.sbomify.com/CVE-2025-26862/index.md)
```

## Sources

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

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