Quick answers
- Is CVE-2026-103242 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-103242 being exploited in the wild.
- How severe is CVE-2026-103242?
- High severity, with a CVSS score of 7.1, published 30 September 2026.
- Which products and versions are affected?
- RPM Project RPM <UNKNOWN>.
- Is there a fix for CVE-2026-103242?
- 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-103242 attacked?
- It is attacked with local access.
- Am I affected by CVE-2026-103242?
- Check whether you run RPM Project RPM at an affected version. 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
A heap-based buffer overflow exists in the hex2binv() function when processing RPMTAG_FILESIGNATURES in a crafted RPM package header with an incorrect type declaration. The wrong type causes allocation of a one-byte buffer while allowing attacker-controlled, hex-decoded content of arbitrary length to be written past the buffer boundary. The flaw is reachable via rpm2cpio, rpm2archive, and rpm -qlvp with untrusted packages; exploitation requires local user interaction and results in reliable crashes with potential for code execution via heap metadata corruption.
Affected products
- RPM Project RPM <UNKNOWN>
Timeline
- 2026-09-30: disclosed