How severe is CVE-2022-32511?

CVE-2022-32511 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2022-32511 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (80th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2022-32511?

CVE-2022-32511 primarily affects Jmespath. In total, 3 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2022-32511?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

When was CVE-2022-32511 published?

CVE-2022-32511 was published on 2022-06-06 and last updated on 2026-06-17.

CVE-2022-32511

CVE-2022-32511 is a critical-severity vulnerability in Jmespath with a CVSS 3.x base score of 9.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: Critical (CVSS 3.x base score 9.8)
CVSS v2: 7.5
EPSS exploit prediction: 2% (80th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Jmespath
Published: 2022-06-06
Last modified: 2026-06-17

Description

jmespath.rb (aka JMESPath for Ruby) before 1.6.1 uses JSON.load in a situation where JSON.parse is preferable.

Frequently asked questions

What is CVE-2022-32511?: jmespath.rb (aka JMESPath for Ruby) before 1.6.1 uses JSON.load in a situation where JSON.parse is preferable.
How severe is CVE-2022-32511?: CVE-2022-32511 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2022-32511 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (80th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2022-32511?: CVE-2022-32511 primarily affects Jmespath. In total, 3 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2022-32511?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2022-32511 published?: CVE-2022-32511 was published on 2022-06-06 and last updated on 2026-06-17.

References

Affected products (3)

cpe:2.3:a:jmespath:jmespath:*:*:*:*:*:ruby:*:*
cpe:2.3:o:fedoraproject:fedora:35:*:*:*:*:*:*:*
cpe:2.3:o:fedoraproject:fedora:36:*:*:*:*:*:*:*

More vulnerabilities in Jmespath

CVE-2026-54133 — Critical (CVSS 9.8): jmespath.php allows users to use JMESPath, software for declaratively specifying how to extract elements from a JSON…

All CVEs affecting Jmespath →