How severe is CVE-2022-37734?

CVE-2022-37734 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2022-37734?

CVE-2022-37734 affects the following packages: com.graphql-java:graphql-java (Maven), com.graphql-java:graphql-java (Maven). Ecosystems affected: Maven.

How do I fix CVE-2022-37734?

Update com.graphql-java:graphql-java to 17.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-37734 is resolved across your whole dependency graph.

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

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

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

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

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

Yes. There are 1 known exploit references for CVE-2022-37734, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

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

CVE-2022-37734 has an EPSS (Exploit Prediction Scoring System) score of 2.8%, placing it in the 87th 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.

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

CVE-2022-37734 was published on September 12, 2022 and was last updated on October 28, 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

HIGH severity

CVE-2022-37734 — graphql-java

HIGHFix: graphql-java/graphql-java#2892

CVE-2022-37734 is a high-severity (CVSS 7.5) vulnerability in com.graphql-java:graphql-java. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for com.graphql-java:graphql-java — see the affected versions and patch details below.

graphql-java vulnerable to Denial of Service via GraphQL query that consumes CPU resources

Also known asGHSA-v62j-cxhh-fq22

Published

Sep 12, 2022

Updated

Oct 28, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

1 known

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

EPSS Exploitation Probability

via FIRST.org ↗

2.8%probability of exploitation in next 30 days

Lower Risk+0.17%

Lower risk than most CVEs87th percentile — riskier than 87% of all scored CVEsHighest risk

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

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected

☕com.graphql-java:graphql-java☕com.graphql-java:graphql-java

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

graphql-java before19.0 is vulnerable to Denial of Service. An attacker can send a malicious GraphQL query that consumes CPU resources. The fixed versions are 19.0 and later, 18.3, and 17.4, and 0.0.0-2022-07-26T05-45-04-226aabd9.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.graphql-java:graphql-java`	all versions	17.4`com.graphql-java:graphql-java:17.4`
☕Maven	`com.graphql-java:graphql-java`	≥ 18.0&&< 18.3	18.3`com.graphql-java:graphql-java:18.3`

Affected Products

1 product · 2 configurations

Application

graphql-javagraphql-java_project

≥ 18.0 && < 18.3

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

graphql-java before19.0 is vulnerable to Denial of Service. An attacker …

github.comNVDSep 2022

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.graphql-java:graphql-java, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.graphql-java:graphql-java to 17.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-37734 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatLow

Product	Fixed in	Advisory
Red Hat build of Eclipse Vert.x 4.3.3	`graphql-java`	RHSA-2022:6757
Red Hat build of Quarkus 2.13.5	see advisory	RHSA-2022:9023
RHINT Service Registry 2.3.0 GA	`graphql-java`	RHSA-2022:6835

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2022-37734 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

7.5/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

High

Raw vector

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

Weaponization

No Nuclei template or Metasploit module yet. 1 public proof-of-concept reference is listed on this page.

OpenSSF Scorecard

Package health score

graphql-java

6.3/10

Code-Review3/10

Maintained10/10

Branch-ProtectionN/A

Assessed Nov 2, 2026

Timeline

Disclosed

Sep 12, 2022

First exploit

Sep 15, 2022

3 days after disclosure — rapid exploitation

Last updated

Oct 28, 2026

Identifiers

CVE-2022-37734

GHSA-v62j-cxhh-fq22

References

Advisorygithub.com · CVE 2022 37734.json Advisorynvd.nist.gov · CVE 2022 37734 Fixgithub.com Reportgithub.com Webgithub.com Websecurity.snyk.io · SNYK JAVA COMGRAPHQLJAVA 3021519 Packagegithub.com · releases Packagegithub.com · graphql java

Related vulnerabilities

This CVE is high severity, in line with the other 2 CVEs affecting graphql-java.

CVE-2024-40094CVE-2023-28867

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 28, 2026

CVE-2022-37734 — graphql-java

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

Fixing This On Your OS

Frequently Asked Questions

Is CVE-2022-37734 in your dependencies?