Openshift vulnerabilitiesAnd the versions its exploited flaws hit.

Product2 known exploited68 versions
The short answer

Openshift is made by Red Hat. We track 177 published vulnerabilities listed under that exact name, across 68 versions. 2 of them are on the list of flaws known to be exploited, the newest added on 10 October 2023. Red Hat lists newer releases under their own names, such as Openshift Container Platform, so check those pages too.

Check your version

The most recent Openshift flaw added to the known-exploited list is CVE-2023-44487, on 10 October 2023. We keep watching the known-exploited list.

Versions

Which versions of Openshift do the exploited flaws hit?

Each exploited flaw lists the versions it affects, as published by the vendor. Find your version, then patch.

  • CVE-2015-5317Exploited list, 12 May 2023

    Jenkins User Interface (UI) Information Disclosure Vulnerability

    up to 3.1

1 more exploited flaw names Openshift without a version of its own, for example as the system other affected software runs on. It is in the list below.

Known exploited

Which Openshift vulnerabilities are being exploited?

2 flaws are on the government list of vulnerabilities known to be exploited. These are the ones criminals are using now, so they go first, whatever their severity score says.

  1. 7.5
    CVE-2023-44487HighKnown exploited
    HTTP/2 Rapid Reset Attack Vulnerability

    HTTP/2 contains a rapid reset vulnerability that allows for a distributed denial-of-service attack (DDoS).

    Chance of use>99%Known exploited since10 Oct 2023
  2. 7.5
    CVE-2015-5317HighKnown exploited
    Jenkins User Interface (UI) Information Disclosure Vulnerability

    Jenkins User Interface (UI) contains an information disclosure vulnerability that allows users to see the names of jobs and builds otherwise inaccessible to them on the "Fingerprints" pages.

    Chance of use23%Known exploited since12 May 2023
Exploit likelihood

Which Openshift flaws are most likely to be used?

Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.

50% or more10% to 49%Under 10%
  1. >99%
    CVE-2023-44487HighKnown exploited

    The HTTP/2 protocol allows a denial of service (server resource consumption) because request cancellation can reset many streams quickly, as exploited in the wild in August through October 2023.

    CVSS7.5Published10 Oct 2023
  2. 98%

    runc through 1.0-rc6, as used in Docker before 18.09.2 and other products, allows attackers to overwrite the host runc binary (and consequently obtain host root access) by leveraging the ability to execute a command...

    CVSS8.6Published11 Feb 2019
  3. 83%

    Multiple unspecified API endpoints in Jenkins before 1.650 and LTS before 1.642.2 allow remote authenticated users to execute arbitrary code via serialized data in an XML file, related to XStream and groovy.util.Expando.

    CVSS8.8Published7 Apr 2016
  4. 38%

    Apache ActiveMQ 5.x before 5.13.0 does not restrict the classes that can be serialized in the broker, which allows remote attackers to execute arbitrary code via a crafted serialized Java Message Service (JMS)...

    CVSS9.8Published8 Jan 2016
  5. 23%
    CVE-2015-5317HighKnown exploited

    The Fingerprints pages in Jenkins before 1.638 and LTS before 1.625.2 might allow remote attackers to obtain sensitive job and build name information via a direct request.

    CVSS7.5Published25 Nov 2015
  6. 12%

    The remoting module in Jenkins before 1.650 and LTS before 1.642.2 allows remote attackers to execute arbitrary code by opening a JRMP listener.

    CVSS9.8Published7 Apr 2016
  7. 8.8%

    A flaw was found in rsync which could be triggered when rsync compares file checksums.

    CVSS7.5Published14 Jan 2025
  8. 8.0%

    The mirroring support (-M, --use-mirrors) in Python Pip before 1.5 uses insecure DNS querying and authenticity checks which allows attackers to perform man-in-the-middle attacks.

    CVSS5.9Published5 Nov 2019
Precursor Intelligence

Running Openshift? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

We track 177 published vulnerabilities listed under the name Openshift, across 68 versions. The most recent Openshift flaw added to the known-exploited list is CVE-2023-44487, on 10 October 2023.

2 are on the list of flaws known to be exploited. The most recently added are CVE-2023-44487 and CVE-2015-5317.

Red Hat also lists Openshift under more specific names, such as Openshift Container Platform and Openshift Application Runtimes. Flaws listed only under those names are counted on their own pages, not here. Open the release you run to see its own list.

Each flaw names its own versions, usually as ranges. The newest, CVE-2015-5317, affects up to 3.1. The versions for every exploited flaw are listed on this page.

Create a Precursor Intelligence account and track Openshift. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.