Quick answers
- Is CVE-2026-113786 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-113786 being exploited in the wild.
- How severe is CVE-2026-113786?
- Medium severity, with a CVSS score of 4, published 21 October 2026.
- Which products and versions are affected?
- Pypdf before 6.21.1; pypdf (PyPI) < 6.21.1, ECOSYSTEM:introduced=0,fixed=6.21.1.
- Is there a fix for CVE-2026-113786?
- Yes. pypdf (PyPI): upgrade to 6.21.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-113786 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-113786?
- Check whether you run Pypdf or pypdf (PyPI) 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.
How to fix
- pypdf (PyPI): upgrade to 6.21.1 or later
pip install "pypdf>=6.21.1"
Technical details
The vulnerability exists in the _xobj_to_image function, which processes DCTDecode-filtered image streams. Without restricting the image format, Pillow's Image.open() sniffs the stream bytes and selects a parser based on file magic bytes rather than the declared format, allowing an attacker to embed non-JPEG data (such as EPS) that triggers external command execution via the EpsImagePlugin. The fix restricts DCTDecode processing to JPEG format only, preventing plugin confusion.
Affected products
- pypdf pypdf before 6.21.1
Identifiers
- CVE-2026-113786
- GHSA-5hx5-vpf9-5wcv
Timeline
- 2026-10-21: disclosed
- 2026-10-17: patched