Skip to main content
CVE-2025-47907VulnerabilityPublished Updated

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

Affects Red HatSource GCVE Database

0
Compare
Authoritative record:CVE-2025-47907· High 7.0

Not known to be exploited · CVSS 7.0 High.

Data as of 1 Nov 2026, 08:20 UTC

CVSS 3.1 base score
7.0High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 34% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Aug 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 31 Oct 2026.

What to do

AI-suggested

A fixed version of OpenShift Container Platform is available in release 4.20.2, which includes updated container images and RPM packages addressing this vulnerability. Users should upgrade their clusters to version 4.20.2 using the OpenShift CLI (oc) or web console following the official upgrade instructions provided by Red Hat. No additional mitigations are specified beyond applying this update.

Description

Red Hat OpenShift Container Platform 4.20.2 includes a security update addressing a race condition vulnerability in the database/sql package related to Postgres scanning (CVE-2025-47907). This update fixes a concurrency issue that could affect the stability or correctness of database operations. Users of OpenShift Container Platform 4.20 are advised to upgrade to this release to apply the fix.

References

Community reviews

Loading reviews…