Quick answers
- Is CVE-2026-100310 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-100310 being exploited in the wild.
- How severe is CVE-2026-100310?
- High severity, with a CVSS score of 7, published 25 September 2026.
- Which products and versions are affected?
- Gnu Libextractor before 1.16.
- Is there a fix for CVE-2026-100310?
- A patch was published on 2026-06-30: Fixed in version 1.16 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-100310 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-100310?
- Check whether you run Gnu Libextractor 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
The vulnerability exists in libextractor's plugin loading mechanism, which respects the LIBEXTRACTOR_PREFIX environment variable even when the calling process is setuid/setgid or running with elevated privileges. An attacker can set LIBEXTRACTOR_PREFIX to point to a directory containing a malicious plugin that gets loaded and executed with the privileges of the setuid/setgid program. Version 1.16 and later disable the use of LIBEXTRACTOR_PREFIX in privileged contexts (setuid/setgid or running as root).
Affected products
- GNU libextractor before 1.16
Timeline
- 2026-09-25: disclosed
- 2026-06-30: patched: Fixed in version 1.16