An issue was discovered in Foxit Reader and PhantomPDF before 10.1.

published 2020-10-02 6y ago modified 2026-06-17 4mo ago also EUVD-2020-19080

cvss: 9.8; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 1.7%; EPSS 1.7% chance of exploitation in 30 days, percentile 77%
public exploits: 0; none known

An issue was discovered in Foxit Reader and PhantomPDF before 10.1. If TslAlloc attempts to allocate thread local storage but obtains an unacceptable index value, V8 throws an exception that leads to a write access violation (and read access violation).

Patch / fix

fixed in 2 links 1

foxitsoftware foxit_reader 10.1
foxitsoftware phantompdf 10.1

foxitsoftware.com/support/security-bulletins.html advisory

Is CVE-2020-26535 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.72% chance of exploitation in the next 30 days, higher than 77% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.1	9.8	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD	2.0	7.5	AV:N/AC:L/Au:N/C:P/I:P/A:P

Classification

Weakness

CWE-787 Out-of-bounds Write

References

foxitsoftware.com /support/security-bulletins.html
patch, vendor-advisory

Sources

CVE List CVE-2020-26535
NVD CVE-2020-26535

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.