CVSS 3.1
6.4 mediumCVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:HMedium (6.4) in redhat process automation manager. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:HExplain CVE-2025-58713 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-58713?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-58713?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-58713 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the NVD's CPE matches.
| Product | Affected |
|---|---|
| redhat:process_automation_manager | 7.0 |
Red Hat rates this Moderate.
Red Hat Product Security has rated this vulnerability as moderate severity for affected products which run on OpenShift. The vulnerability allows for potential privilege escalation within a container, but OpenShift's default, multi-layered security posture effectively mitigates this risk.
The primary controls include the default Security Context Constraints (SCC), which severely limit a container's permissions from the start, and SELinux, which enforces mandatory access control to ensure strict isolation. While other container runtime environments may have different controls available and require case-by-case analysis, OpenShift's built-in defenses are designed to prevent this type of attack.
Out of Box RHEL configuration isolates a single process inside a container. Unless multiple processes are packaged inside a single container, that defeats the principle behind containerization, this bug can not be used to meaningfully escalate privileges.
Also, RHEL, and any common linux distributions do NOT add any additional users to the root group. The presence of the root group is strictly due to conformance with POSIX permission management requirements and can be considered to be an artifact of filesystem permission limitations.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Process Automation 7 | rhpam-businesscentral-monitoring-rhel8 | Under investigation | |
| Red Hat Process Automation 7 | rhpam-businesscentral-rhel8 | Under investigation | |
| Red Hat Process Automation 7 | rhpam-controller-rhel8 | Under investigation | |
| Red Hat Process Automation 7 | rhpam-dashbuilder-rhel8 | Under investigation | |
| Red Hat Process Automation 7 | rhpam-kieserver-rhel8 | Under investigation | |
| Red Hat Process Automation 7 | rhpam-process-migration-rhel8 | Under investigation |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2025-58713.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.