Code execution via tar member macro injection
Published Aug 24, 2026 · Updated Aug 24, 2026
Code injection in RPM rpmbuild tarball processing allows attackers to execute arbitrary code via crafted source archives. getTarSpec() inserts an archive-controlled .spec member name into a %{basename:...} expression passed to rpmExpand(), allowing a closing brace to introduce Lua or other RPM macros. Execution requires a user or build system to process the archive in rpmbuild tarball mode and occurs with that process's privileges.
Summary
What happened
Code injection in RPM rpmbuild tarball processing allows attackers to execute arbitrary code via crafted source archives. getTarSpec() inserts an archive-controlled .spec member name into a %{basename:...} expression passed to rpmExpand(), allowing a closing brace to introduce Lua or other RPM macros. Execution requires a user or build system to process the archive in rpmbuild tarball mode and occurs with that process's privileges.
The record
- CVE
- CVE-2026-78367
- Published
- Aug 24, 2026
- Updated
- Aug 24, 2026
- Vendor
- 389 Directory Server
- Product
- Red Hat Enterprise Linux 10
- Classifications
- CWE-94, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 24, 2026CVE publishedPublication date reported by the CVE source.
- Aug 24, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- reproducer-member-name.shproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo