CVE-2022-22817

PIL.ImageMath.eval in Pillow before 9.0.0 allows evaluation of arbitrary expressions, such as ones that use the Python exec method. A lambda expression could also be used.

Published: 2022-01-10 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2022-22817 is rated High Risk (70.4/100): CVSS Critical severity, with medium exploitation likelihood (EPSS 3.40%). High exploitation likelihood—assess exposure and prioritize remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2022-22817

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 2.78% 3.40% +0.62%
2 2025-12-28 3.16% 2.78% -0.38%
3 2025-12-27 — 3.16% —

Full EPSS history (33 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2022-22817

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
9.8 3.1 CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 5.9 [email protected]
9.8 3.1 CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 5.9 134c704f-9b21-4f2e-91b3-4a467353bcc0
7.5 2.0 HIGH
AV:N/AC:L/Au:N/C:P/I:P/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:P)
Partial availability impact.
 10.0 6.4 [email protected]

Weakness enumeration for CVE-2022-22817

GitHub Security Advisory for CVE-2022-22817

GHSA-8vj2-vxx3-667w · Severity: critical · Ecosystem: pip — Arbitrary expression injection in Pillow

OS Trackers for CVE-2022-22817

vendor priority summary link
alpine — CVE-2022-22817: 1 source package rows (py3-pillow); 8 state rows across 7 repos (3.17-community, 3.18-community, 3.19-community, 3.20-community, 3.21-community, 3.22-community, edge-community); fixed 8, open 0. https://security.alpinelinux.org/vuln/CVE-2022-22817
debian not yet assigned CVE-2022-22817 not yet assigned priority: Debian including 1 source packages (pillow), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2022-22817
gentoo high CVE-2022-22817: 1 GLSA(s) (202211-10), 1 atom(s) (dev-python/pillow); latest impact high. https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2022-22817
redhat high — https://access.redhat.com/security/cve/CVE-2022-22817
suse medium CVE-2022-22817 severity moderate: SUSE including 86 source package names (ardana-barbican-9.0+git.1644879908.8a641c1-3.13.1, grafana-6.7.4-3.26.1, …), 128 product×package rows across 10 product lines (HPE Helion OpenStack 8, SUSE Liberty Linux 7, … (10 product lines)): Fixed 128. https://www.suse.com/security/cve/CVE-2022-22817/
ubuntu medium CVE-2022-22817 medium priority: Ubuntu including 3 source packages (pillow, pillow-python2, python-imaging), 45 status rows across 15 suites (bionic, focal, hirsute, impish, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): DNE 27, not-affected 10, released 5, needs-triage 2, ignored 1. https://ubuntu.com/security/CVE-2022-22817

Affected software / configurations for CVE-2022-22817

Vendor Product Version Raw CPE
python pillow < 9.0.1 cpe:2.3:a:python:pillow:*:*:*:*:*:*:*:*
debian debian_linux 9.0 cpe:2.3:o:debian:debian_linux:9.0:*:*:*:*:*:*:*
debian debian_linux 10.0 cpe:2.3:o:debian:debian_linux:10.0:*:*:*:*:*:*:*
debian debian_linux 11.0 cpe:2.3:o:debian:debian_linux:11.0:*:*:*:*:*:*:*

References for CVE-2022-22817

cvelogic Threat Intelligence