Medium [CVE-2026-50014] Arbitrary Code Execution via Malicious Lockfile
This medium-severity Red Hat Linux advisory covers CVE-2026-50014 affecting Red Hat AMQ Broker 7, Red Hat Build of Keycloak, Red Hat JBoss Enterprise Application Platform 8.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
Summary
pnpm is a package manager. Prior to 10.34.0 and 11.4.0, pnpm passes the lockfile-controlled git resolution.commit value to git fetch without a -- separator or commit-format validation.
For git dependencies fetched through the shallow-fetch path, a malicious lockfile can replace the expected 40-character commit hash with a Git option such as --upload-pack=. For SSH and local transports, --upload-pack can execute the supplied command.
HTTPS transports ignore --upload-pack, so the practical attack surface is primarily SSH or local git dependencies. This vulnerability is fixed in 10.34.0 and 11.4.0.
An attacker could exploit this vulnerability by providing a malicious lockfile, which could lead to arbitrary code execution. This Moderate severity flaw in pnpm allows for arbitrary code execution.
The vulnerability arises from pnpm's improper handling of git dependency commit values from a malicious lockfile, specifically when using SSH or local git transports.
Red Hat products utilizing pnpm, such as Konflux, Red Hat Build of Keycloak, Enterprise Application Platform, and Red Hat AMQ, are affected if they process untrusted pnpm-lock.yaml files with SSH or local git dependencies. Red Hat severity: Moderate — CVSS 6.4 (CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:N).
Weakness: CWE-78.
Is CVE-2026-50014 exploited?
No exploitation is reported in the sources VulniPulse tracks: CVE-2026-50014 is not in the CISA KEV catalog (checked ) and this advisory does not report exploitation. That is not proof the vulnerability cannot be exploited.
How do I fix CVE-2026-50014?
Upgrade to a fixed release named by Red Hat:
- 10.34.0
- 11.4.0
Confirm against the vendor advisory before you patch.
- < 10.34.0
- < 11.4.0
Official advisory · high-confidence parse· fetched 14 days ago·verify at source
- 10.34.0
- 11.4.0
Official advisory · high-confidence parse· fetched 14 days ago·verify at source
Mitigation checklist
- Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
Official advisory · high-confidence parse· fetched 14 days ago·verify at source
Get an email when Red Hat publishes the next one.
See Red Hat's last 90 days of advisories first. Then choose one product with live alerts free for life, or a free month of real-time alerts on everything with the severity, the fixed version and the vendor's link (card needed, then US$15/month; we email you before the first charge).
More Red Hat Linux advisories
- CVE-2026-34197Apr 7, 2026RCE via crafted discovery URI in Jolokia JMX-HTTP bridge
- CVE-2026-119977Oct 31, 2026Arbitrary code execution via predictable upgrade staging paths
- CVE-2026-111497Oct 22, 2026Out-of-Bounds Write in Google Brotli Decoder
- CVE-2026-109619Oct 21, 2026fatal error handling retains stale request state leading to use-after-free
- CVE-2026-109618Oct 21, 2026OOM bailout during request parsing leads to memory corruption and RCE
- CVE-2026-97229Oct 13, 2026integer overflow issue in CI/CD regular expression compiler
iPhone and Android apps · New on the App Store
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.