Quick answers
- Is CVE-2026-80327 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-80327 being exploited in the wild.
- How severe is CVE-2026-80327?
- Informational severity, published 6 October 2026.
- Which products and versions are affected?
- Ping Identity PingGateway 7.1.0 and later, 2023.2.0–2024.11.1, 2025.3.0–2025.11.1.
- Is there a fix for CVE-2026-80327?
- Yes: fixed in PingGateway 2024.11.2, 2025.11.2, 2026.3.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-80327 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-80327?
- Check whether you run Ping Identity PingGateway at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: PingGateway 2024.11.2, 2025.11.2, 2026.3.0
Technical details
An open redirect vulnerability exists in the PingGateway Fragment Filter feature, allowing attackers to craft malicious URLs that redirect users to external sites. The vulnerability affects versions 7.1.0 and later, 2023.2.0–2024.11.1, and 2025.3.0–2025.11.1. A fix is available in versions 2024.11.2, 2025.11.2, and 2026.3.0 or later.
Affected products
- Ping Identity PingGateway 7.1.0 and later, 2023.2.0–2024.11.1, 2025.3.0–2025.11.1
Timeline
- 2026-10-06: disclosed