CVE-2025-57852 json
Openshift-ai: privilege escalation via excessive /etc/passwd permissions
published 2025-09-30 13 mo ago modified 2026-06-17 4 mo ago also EUVD-2025-31743
- cvss
- 6.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 4%
- public exploits
- 0
- none known
Summary
A container privilege escalation flaw was found in KServe ModelMesh container images. This issue stems from the /etc/passwd file being created with group-writable permissions during build time. In certain conditions, an attacker who can execute commands within an affected container, even as a non-root user, can 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.
Patch / fix
- Red Hat Red Hat OpenShift AI 2.16 sha256:97e2bd9b587f08e135a9aeb9b3e0dc6eafa1a9bdacbb5ecb681ce9bd5aa37fc9
- Red Hat Red Hat OpenShift AI 2.19 sha256:53ac36baa374159b9065c718a9ede821bbb61d9ebe9502b2243e0a9f7aca0d16
- Red Hat Red Hat OpenShift AI 2.21 sha256:687c8eeed55f021ecaab1307f0e88b5b16d91f72d63b3d7168d7bbee90e8947b
- Red Hat Red Hat OpenShift AI 2.22 sha256:1709fa3c79aad4ba7eb9be8299949396092c8e20210124e0c0936385bc04e839
- Red Hat Red Hat OpenShift AI 2.24 sha256:92629b1462ca2ed121dd2f3069a005d78e00e1344d330d6a8710f53ec58b74b8
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2025-57852 updated cvss 6.4
openshift-ai: privilege escalation via excessive /etc/passwd permissions
-
Red Hat OpenShift AI 2.16 rhoaifixed: vendor fix RHSA-2025:16981
-
Red Hat OpenShift AI 2.19 rhoaifixed: vendor fix RHSA-2025:16984
-
Red Hat OpenShift AI 2.21 rhoaifixed: vendor fix RHSA-2025:16983
-
Red Hat OpenShift AI 2.22 rhoaifixed: vendor fix RHSA-2025:16982
-
Red Hat OpenShift AI 2.24 rhoai v2.24.0-1759255555fixed: vendor fix RHSA-2025:17501
-
Red Hat OpenShift AI 2.16 rhoai v2.16.3-1758698212, rhoai v2.16.3-1758715861, rhoai v2.16.3-1758720446 Red Hat OpenShift AI 2.19 rhoai v2.19.3-1758705248, rhoai v2.19.3-1758715871, rhoai v2.19.3-1758720462 Red Hat OpenShift AI 2.21 rhoai v2.21.1-1758709863, rhoai v2.21.1-1758715880, rhoai v2.21.1-1758724953 Red Hat OpenShift AI 2.22 rhoai v2.22.2-1758733209, rhoai v2.22.2-1758779769, rhoai v2.22.2-1758799703 Red Hat OpenShift AI 2.24 rhoai 0.0-1756488283, rhoai v2.24.0-1754935969, rhoai v2.24.0-1754935971, rhoai v2.24.0-1755221760, rhoai v2.24.0-1755688864, rhoai v2.24.0-1755740117, +33 morenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 13 mo ago
Exploit prediction
0.16% chance of exploitation in the next 30 days, higher than 4% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.4 | CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Red Hat Red Hat OpenShift AI 2.16
- Red Hat Red Hat OpenShift AI 2.19
- Red Hat Red Hat OpenShift AI 2.21
- Red Hat Red Hat OpenShift AI 2.22
- Red Hat Red Hat OpenShift AI 2.24
Classification
- Weakness
-
- CWE-276 Incorrect Default Permissions
References
-
access.redhat.com
/errata/RHSA-2025:16981
vendor-advisory
-
access.redhat.com
/errata/RHSA-2025:16982
vendor-advisory
-
access.redhat.com
/errata/RHSA-2025:16983
vendor-advisory
-
access.redhat.com
/errata/RHSA-2025:16984
vendor-advisory
-
access.redhat.com
/errata/RHSA-2025:17501
vendor-advisory
-
access.redhat.com
/security/cve/CVE-2025-57852
vdb-entry
-
bugzilla.redhat.com
/show_bug.cgi?id=2391105
issue-tracking
Sources
- CVE List CVE-2025-57852
- NVD CVE-2025-57852
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.