How severe is CVE-2024-23316?

CVE-2024-23316 has a CVSS 4.0 base score of 8.8, rated high severity.

Is CVE-2024-23316 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (42nd percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2024-23316?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

Does CVE-2024-23316 have an EU (EUVD) identifier?

Yes. CVE-2024-23316 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2024-20834.

When was CVE-2024-23316 published?

CVE-2024-23316 was published on 2024-05-31 and last updated on 2026-06-17.

CVE-2024-23316

CVE-2024-23316 is a high-severity vulnerability with a CVSS 4.0 base score of 8.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-444.

Key facts

Severity: High (CVSS 4.0 base score 8.8)
EPSS exploit prediction: 1% (42nd percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2024-20834
Weakness: CWE-444
Published: 2024-05-31
Last modified: 2026-06-17

Description

HTTP request desynchronization in Ping Identity PingAccess, all versions prior to 8.0.1 affected allows an attacker to send specially crafted http header requests to create a request smuggling condition for proxied requests.

Frequently asked questions

What is CVE-2024-23316?: HTTP request desynchronization in Ping Identity PingAccess, all versions prior to 8.0.1 affected allows an attacker to send specially crafted http header requests to create a request smuggling condition for proxied requests.
How severe is CVE-2024-23316?: CVE-2024-23316 has a CVSS 4.0 base score of 8.8, rated high severity.
Is CVE-2024-23316 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (42nd percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2024-23316?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2024-23316 have an EU (EUVD) identifier?: Yes. CVE-2024-23316 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2024-20834.
When was CVE-2024-23316 published?: CVE-2024-23316 was published on 2024-05-31 and last updated on 2026-06-17.

References

Other CWE-444 (HTTP Request/Response Smuggling) vulnerabilities

CVE-2025-1867 — Critical (CVSS 10.0): Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') vulnerability in ithewei libhv allows…
CVE-2022-22536 — Critical (CVSS 10.0): SAP NetWeaver Application Server ABAP, SAP NetWeaver Application Server Java, ABAP Platform, SAP Content Server 7.53…
CVE-2018-3907 — Critical (CVSS 10.0): An exploitable vulnerability exists in the REST parser of video-core's HTTP server of the Samsung SmartThings Hub…
CVE-2025-55315 — Critical (CVSS 9.9): Inconsistent interpretation of http requests ('http request/response smuggling') in ASP.NET Core allows an authorized…
CVE-2020-15049 — Critical (CVSS 9.9): An issue was discovered in http/ContentLengthInterpreter.cc in Squid before 4.12 and 5.x before 5.0.3. A Request…
CVE-2026-13763 — Critical (CVSS 9.8): Inconsistent interpretation of HTTP/2 requests in AWS Application Load Balancer with AWS WAF enabled might allow remote…

Browse all CWE-444 (HTTP Request/Response Smuggling) vulnerabilities →