4 Openshift 4

Don't miss out!

Thousands of developers use stack.watch to stay informed.
Get an email whenever new security vulnerabilities are reported in Openshift 4.

By the Year

In 2026 there have been 0 vulnerabilities in Openshift 4. Last year, in 2025 4 had 2 security vulnerabilities published. Right now, 4 is on track to have less security vulnerabilities in 2026 than it did last year.

Year Vulnerabilities Average Score
2026 0 0.00
2025 2 6.50

It may take a day or so for new 4 vulnerabilities to show up in the stats or in the list of recent security vulnerabilities. Additionally vulnerabilities may be tagged under a different product or component name.

Recent Openshift 4 Security Vulnerabilities

Operator SDK <0.15.2 RCE via insecure user_setup /etc/passwd
CVE-2025-7195 5.2 - Medium - August 07, 2025

Early versions of Operator-SDK provided an insecure method to allow operator containers to run in environments that used a random UID. Operator-SDK before 0.15.2 provided a script, user_setup, which modifies the permissions of the /etc/passwd file to 664 during build time. Developers who used Operator-SDK before 0.15.2 to scaffold their operator may still be impacted by this if the insecure user_setup script is still being used to build new container images. In affected images, the /etc/passwd file is created during build time with group-writable permissions and a group ownership of root (gid=0). An attacker who can execute commands within an affected container, even as a non-root user, may be able to leverage their membership in the root group to modify the /etc/passwd file. This could allow the attacker to add a new user with any arbitrary UID, including UID 0, leading to full root privileges within the container.

Incorrect Default Permissions

Integer Overflow in libarchive RAR Reader Causes Double-Free
CVE-2025-5914 7.8 - High - June 09, 2025

A vulnerability has been identified in the libarchive library, specifically within the archive_read_format_rar_seek_data() function. This flaw involves an integer overflow that can ultimately lead to a double-free condition. Exploiting a double-free vulnerability can result in memory corruption, enabling an attacker to execute arbitrary code or cause a denial-of-service condition.

Double-free

Stay on top of Security Vulnerabilities

Want an email whenever new vulnerabilities are published for Openshift 4 or by Openshift? Click the Watch button to subscribe.

Openshift
Vendor

Openshift 4
Product

subscribe