CVE-2024-5037VulnerabilityPublished 3 Jul 2024Updated 11 Aug 2026

Red Hat Security Advisory: OpenShift Container Platform 4.16.1 bug fix and security update

Affects Red HatSource GCVE Database

Mentioned vulnerabilities

CVE-2024-26147

Authoritative record:CVE-2024-5037· High 7.5

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.8% chance of exploitation in 30 days – higher than 56% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

Disclosed: evidence found.
CVE published 5 Jun 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 26 Oct 2026.

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

Affected software

Product	Affected	Fixed in
GitHubopenshift/telemeter`pkg:github/openshift/telemeter`Other threats	Affected =4.16	Fixed in–

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 OpenShift Container Platform 4.16.1 containing fixes for these vulnerabilities. Users should upgrade to this version using the OpenShift CLI (oc) or web console as soon as the updated packages and container images are available in their release channel. Detailed upgrade instructions are available at Red Hat's official documentation. There is no indication that these issues are already mitigated or require no action; therefore, applying the official update is the recommended remediation.

Description

Red Hat OpenShift Container Platform 4.16.1 includes security updates addressing two vulnerabilities: CVE-2024-5037, where the issuer (iss) check during JWT authentication in openshift/telemeter can be bypassed, and CVE-2024-26147, a Helm vulnerability causing a panic due to missing YAML content. These issues affect OpenShift Container Platform 4.16 deployments. Users are advised to upgrade to the updated packages and container images provided in version 4.16.1 to mitigate these vulnerabilities.

Impact

The bypass of the issuer check in JWT authentication (CVE-2024-5037) could allow unauthorized access or actions by circumventing authentication controls in the telemeter component. The Helm vulnerability (CVE-2024-26147) can cause application panic, potentially leading to denial of service or instability in deployments using Helm charts. Both vulnerabilities affect the security and stability of OpenShift Container Platform 4.16 environments if unpatched.

CWE-290Authentication Bypass by Spoofing (opens in a new tab)
Base weaknessOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
This attack-focused weakness is caused by incorrectly implemented authentication schemes that are subject to spoofing attacks.
OWASP Cheat Sheets
REST Security (opens in a new tab)
JSON Web Token for Java (opens in a new tab)
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V3.5.1 (opens in a new tab)
V2.8.5 (opens in a new tab)
V2.8.4 (opens in a new tab)
Attack patterns
Creating a Rogue Certification Authority Certificate (opens in a new tab)
Web Services API Signature Forgery Leveraging Hash Function Extension Weakness (opens in a new tab)
Signature Spoof (opens in a new tab)
Signature Spoofing by Misrepresentation (opens in a new tab)
Session Credential Falsification through Prediction (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-457Use of Uninitialized Variable (opens in a new tab)
Variant weaknessLikelihood of exploit: High
The code uses a variable that has not been initialized, leading to unpredictable or unintended results.
Implementation · Attack Surface Reduction
Ensure that critical variables are initialized before first use.
Build and Compilation · Compilation or Build Hardening
Most compilers will complain about the use of uninitialized variables if warnings are turned on.
Implementation · Operation
When using a language that does not require explicit declaration of variables, run or compile the software in a mode that reports undeclared or unknown variables. This may indicate the presence of a typographic error in the variable's name.
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 11 Aug 2026, 20:56 UTC

WeaknessesCWE-290, CWE-457

Technical details

References

Community reviews

Related threats