Arbitrary Code Injection Affecting rpm-software-management/rpm package, versions [0,]
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-UNMANAGED-RPMSOFTWAREMANAGEMENTRPM-19427922
- published29 Aug 2026
- disclosed24 Aug 2026
- creditUnknown
Introduced: 24 Aug 2026
NewCVE-2026-78367 (opens in a new tab)How to fix?
There is no fixed version for rpm-software-management/rpm.
Overview
Affected versions of this package are vulnerable to Arbitrary Code Injection in the getTarSpec function when processing a crafted source archive member name. An attacker can execute arbitrary code with the privileges of the rpmbuild process by supplying a specially crafted source tarball that is processed in tarball mode (such as -ts, -ta, or -tb). This is only exploitable if an attacker-controlled tarball is processed by rpmbuild in tarball mode.
Workaround
This vulnerability can be mitigated by not processing untrusted tarballs with rpmbuild -ta/-tb/-ts, extracting and inspecting archives first (rejecting member names containing }, %, or {), or building from a reviewed .spec file outside tarball mode. Prefer isolated builders (mock/container) for any untrusted packaging-related work.