dbcve.org
Process Automation ManagerApplication · Redhat

CVE-2025-58713

MEDIUM · 6.4 CVSS v3.1 Published 2026-04-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
66/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A container privilege escalation flaw was found in certain Red Hat Process Automation Manager 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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is a container privilege escalation vulnerability where the /etc/passwd file is created with group-writable permissions (e.g., 0664) during the image build process. An attacker with the ability to execute commands inside the container as a non-root user who is a member of the root group can modify /etc/passwd to add a new user with UID 0, effectively gaining root privileges within the container.

MitigationRebuild the affected container images with corrected file permissions for /etc/passwd (remove group-write bit, e.g., set to 0644 or 0640), or update to vendor-patched images. Audit existing deployed containers for this permission misconfiguration.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Process Automation ManagerApplication
Affected:= 7.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
High
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed version of Red Hat Process Automation Manager
    Check the product version by inspecting the image labels or version files. For container images, run: docker inspect <image> | grep -i version or check /etc/*-release. For installed packages, run: rpm -qa | grep -i process-automation-manager
    Affected if The version is exactly 7.0 (Redhat Process Automation Manager 7.0)
  2. Test write access to /etc/passwd
    As the current user, attempt to write to /etc/passwd: touch /etc/passwd.test or echo 'test' >> /etc/passwd (use a test file, not the actual file)
    Affected if The current user can successfully write to /etc/passwd or the directory containing it, indicating group-write permissions enable modification

A user is affected if they are running Red Hat Process Automation Manager version 7.0, /etc/passwd has group-write permissions enabled, and the current non-root user is a member of the root group (allowing modification of /etc/passwd to add UID 0 users).

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Rebuild the affected container images with corrected file permissions for /etc/passwd (remove group-write bit, e.g., set to 0644 or 0640), or update to vendor-patched images. Audit existing deployed containers for this permission misconfiguration.

Recommended fix Moderate confidence

Process Automation Manager 7.0 with corresponding Red Hat errata applied (consult access.redhat.com for specific errata ID)

  1. Contact Red Hat support or consult access.redhat.com for the specific errata/patch addressing CVE-2025-58713
  2. Obtain the updated Process Automation Manager 7.0 container image that contains the fixed /etc/passwd file permissions
  3. Pull the updated container image from Red Hat's registry
  4. Re-deploy the container using the updated image, ensuring all configurations and data are properly migrated
  5. Verify that the /etc/passwd file in the new container no longer has group-writable permissions (permissions should be 644 or stricter)
Caveat Consult Red Hat release notes for any configuration or compatibility changes in the updated image

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Process Automation Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-58713 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-58713 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data