Quick answers
- Is CVE-2026-95521 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-95521 being exploited in the wild.
- How severe is CVE-2026-95521?
- High severity, with a CVSS score of 7.8, published 24 September 2026.
- Which products and versions are affected?
- RPM project RPM.
- Is there a fix for CVE-2026-95521?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-95521 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-95521?
- Check whether you run RPM Project RPM. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a command injection flaw (CWE-78) in RPM's source file relocation logic, triggered when spec or source file basenames contain %() macro constructs. When processing untrusted source RPMs, the vulnerable code passes unsanitized filenames to popen(), allowing shell command execution. The flaw requires user interaction to install or rebuild a malicious .src.rpm and is not exposed as a network service.
Affected products
- RPM project RPM
Timeline
- 2026-09-24: disclosed