CVE-2024-49768VulnerabilityPublished 20 Nov 2024Updated 3 Jul 2026

Red Hat Security Advisory: OpenShift Container Platform 4.16.23 packages and security update

Affects Red HatSource GCVE Database

Mentioned vulnerabilities

CVE-2024-49769

Not known to be exploited : upgrade to 4.16.23 soon.

Data as of 25 Oct 2026, 19:02 UTC

Severity

High

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS: 0.4% chance of exploitation in 30 days – higher than 41% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 4.16.23

Exploitation evidence

Disclosed: evidence found.
CVE published 20 Nov 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade redhat/openshift-container-platform to 4.16.23.

Affected software

Product	Affected	Fixed in
Red Hatredhat/openshift-container-platform`pkg:rpm/redhat/openshift-container-platform`Other threats	Affected <4.16.23	Fixed in 4.16.23

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Red Hat has released updated packages and container images in OpenShift Container Platform 4.16.23 that fix these vulnerabilities. Upgrade instructions are available in Red Hat's documentation. Patch status is confirmed with an official fix available. No additional mitigation steps are indicated beyond applying the updates.

Description

Red Hat OpenShift Container Platform is Red Hat's cloud computing Kubernetes application platform solution designed for on-premise or private cloud deployments. This advisory contains the RPM packages for Red Hat OpenShift Container Platform 4.16.23. See the following advisory for the container images for this release: https://access.redhat.com/errata/RHSA-2024:9615 Security Fix(es): * waitress: python-waitress: request processing race condition in HTTP pipelining with invalid first request (CVE-2024-49768) * waitress: Waitress has a denial of service leading to high CPU usage/resource exhaustion (CVE-2024-49769) For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section. To check for available updates, use the OpenShift CLI (oc) or web console. Instructions for upgrading a cluster are available at https://docs.openshift.com/container-platform/4.16/updating/updating_a_cluster/updating-cluster-cli.html

Impact

The vulnerabilities can lead to denial of service conditions in OpenShift Container Platform 4.16 by causing race conditions in HTTP request processing and high CPU/resource exhaustion. This may degrade platform availability and performance. No known exploits in the wild have been reported at this time.

Summary

This advisory covers security fixes in Red Hat OpenShift Container Platform 4.16.23 for two vulnerabilities in the python-waitress HTTP server component. CVE-2024-49768 is a race condition during HTTP pipelining when processing an invalid first request, and CVE-2024-49769 is a denial of service vulnerability that can lead to high CPU usage and resource exhaustion. These vulnerabilities affect the HTTP request handling in waitress, potentially impacting service availability. Red Hat has released updated RPM packages and container images to address these issues. The advisory recommends upgrading OpenShift Container Platform 4.16 clusters to these updated versions using the OpenShift CLI or web console. Detailed upgrade instructions are provided in the official Red Hat documentation.

CWE-444Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') (opens in a new tab)
Base weaknessOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product acts as an intermediary HTTP agent (such as a proxy or firewall) in the data flow between two entities such as a client and server, but it does not interpret malformed HTTP requests or responses in ways that are consistent with how the messages will be processed by those entities that are at the ultimate destination.
Implementation
Use a web server that employs a strict HTTP parsing procedure, such as Apache.
Implementation
Use only SSL communication.
Implementation
Terminate the client session after each request.
OWASP Cheat Sheets
REST Assessment (opens in a new tab)
REST Security (opens in a new tab)
Cross-Site Request Forgery Prevention (opens in a new tab)
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V13.2.5 (opens in a new tab)
Attack patterns
HTTP Response Smuggling (opens in a new tab)
HTTP Request Smuggling (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-772Missing Release of Resource after Effective Lifetime (opens in a new tab)
Base weaknessLikelihood of exploit: High
The product does not release a resource after its effective lifetime has ended, i.e., after the resource is no longer needed.
Requirements · Language Selection
Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Implementation
It is good practice to be responsible for freeing all resources you allocate and to be consistent with how and where you free resources in a function. If you allocate resources that you intend to free upon completion of the function, you must be sure to free the resources at all exit points for that function including…
Operation · Architecture and Design · Resource Limitation
Use resource-limiting settings provided by the operating system or environment. For example, when managing system resources in POSIX, setrlimit() can be used to set limits for certain types of resources, and getrlimit() can determine how many resources are available.
Attack patterns
HTTP DoS (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 3 Jul 2026, 23:05 UTC

WeaknessesCWE-444, CWE-772

Technical details

References

Community reviews

Related threats