How severe is CVE-2022-0671?

CVE-2022-0671 has a CVSS score of 9.1/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2022-0671?

CVE-2022-0671 affects the following packages: org.eclipse.lemminx:lemminx-parent (Maven). Ecosystems affected: Maven.

How do I fix CVE-2022-0671?

Update org.eclipse.lemminx:lemminx-parent to 0.19.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-0671 is resolved across your whole dependency graph.

How do I detect CVE-2022-0671 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.eclipse.lemminx:lemminx-parent, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2022-0671 if there is no patch (or I can't update yet)?

Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

Is CVE-2022-0671 actively exploited in the wild?

No public exploit code has been indexed for CVE-2022-0671 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2022-0671?

CVE-2022-0671 has an EPSS (Exploit Prediction Scoring System) score of 1.3%, placing it in the 69th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2022-0671?

CVE-2022-0671 is classified as Server-Side Request Forgery (SSRF) (CWE-918), Uncontrolled Resource Consumption (CWE-400). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2022-0671 published, and has it been updated?

CVE-2022-0671 was published on February 18, 2022 and was last updated on August 12, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

CRITICAL severity

CVE-2022-0671 — lemminx-parent

CRITICAL

CVE-2022-0671 is a critical-severity (CVSS 9.1) Server-Side Request Forgery (SSRF) vulnerability in org.eclipse.lemminx:lemminx-parent. A fix is available for org.eclipse.lemminx:lemminx-parent — see the affected versions and patch details below.

Server-Side Request Forgery and Uncontrolled Resource Consumption in LemMinX

Also known asGHSA-52vv-3vf7-f7wh

Published

Feb 18, 2022

Updated

Aug 12, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs69th percentile — riskier than 69% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2022-0671 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected

☕org.eclipse.lemminx:lemminx-parent

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

A flaw was found in vscode-xml in versions prior to 0.19.0. Schema download could lead to blind SSRF or DoS via a large file.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.eclipse.lemminx:lemminx-parent`	all versions	0.19.0`org.eclipse.lemminx:lemminx-parent:0.19.0`

Affected Products

1 product · 1 configurations

Application

vscode-xmlredhat

< 0.19.0

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.eclipse.lemminx:lemminx-parent, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.eclipse.lemminx:lemminx-parent to 0.19.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-0671 is resolved across your whole dependency graph.
Workarounds
Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

Frequently Asked Questions

A flaw was found in vscode-xml in versions prior to 0.19.0. Schema download could lead to blind SSRF or DoS via a large file.

O3 Security · Impact-Aware SCA

Is CVE-2022-0671 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

9.1/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

High

Raw vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H

CWE Classification

CWE-918Server-Side Request Forgery (SSRF)CWE-400Uncontrolled Resource Consumption

Weaponization

No known public exploit tooling found.

Timeline

Disclosed

Feb 18, 2022

Last updated

Aug 12, 2026

Identifiers

CVE-2022-0671

GHSA-52vv-3vf7-f7wh

References

Advisorygithub.com Advisorynvd.nist.gov Webgithub.com Webgithub.com Webgithub.com Packagegithub.com

Related vulnerabilities

Also affects lemminx-parent

This CVE is critical severity — higher than any of the other 2 CVEs affecting lemminx-parent (highest there: moderate).

CVE-2022-0673CVE-2022-0672

Same weakness: CWE-918

This CVE is critical severity — higher than any of the other 6 CVEs with CWE-918 (highest there: high).

GHSA-39wr-7q6h-cf68GHSA-jgh3-fggc-mcpmCVE-2026-85732CVE-2026-59823CVE-2026-61793CVE-2026-73247Browse all CWE-918

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedAug 12, 2026

CVE-2022-0671 — lemminx-parent

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2022-0671 in your dependencies?