{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-58712 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-58712 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-58712 is a medium-severity vulnerability in Red Hat RHEL-9 based Middleware Containers, published on 22 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-58712 and fix it if it is affected.\n\nWhat it is: CVE-2025-58712 is a medium-severity vulnerability in Red Hat RHEL-9 based Middleware Containers, published on 22 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-58712 in the wild and no public exploit code.\n\nAffected product: Red Hat RHEL-9 based Middleware Containers. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-58712/ (Markdown: https://insights.sbomify.com/CVE-2025-58712/index.md)","id":"CVE-2025-58712","markdown":"https://insights.sbomify.com/CVE-2025-58712/index.md","name":"CVE-2025-58712","record":{"aliases":["GHSA-r36m-fwrr-9f4g"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"patch","impacts":["privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"AMQ Broker container","requires_auth":"high_privilege","summary":"Attackers with container access can escalate to root by modifying the group-writable /etc/passwd file in AMQ Broker images.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[],"cvss":{"score":6.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-276","name":"Incorrect Default Permissions"}],"description":"A container privilege escalation flaw was found in certain AMQ Broker 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Amq: privilege escalation via excessive /etc/passwd permissions","id":"CVE-2025-58712","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"Rhpam: privilege escalation via excessive /etc/passwd permissions","id":"CVE-2025-58713"},"packages":[],"prev":{"headline":"WordPress Blog Designer PRO plugin \u003c= 3.4.8 - Broken Access Control vulnerability","id":"CVE-2025-58711"},"products":["RHEL-9 based Middleware Containers","Red Hat AMQ Broker 7","activemq-artemis"],"published":"2025-10-22","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-03-06","vendors":["Red Hat","apache"]},"summary":"Attackers with container access can escalate to root by modifying the group-writable /etc/passwd file in AMQ Broker images.","url":"https://insights.sbomify.com/CVE-2025-58712/"}