What is GHSA-QC22-QWM9-J8RX?

GHSA-QC22-QWM9-J8RX is a critical-severity improper input validation vulnerability in npm-groovy-lint (npm), affecting versions < 9.1.0. It is fixed in 9.1.0. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.

Which versions of npm-groovy-lint are affected by GHSA-QC22-QWM9-J8RX?

npm-groovy-lint (npm) versions < 9.1.0 is affected.

Is there a fix for GHSA-QC22-QWM9-J8RX?

Yes. GHSA-QC22-QWM9-J8RX is fixed in 9.1.0. Upgrade to this version or later.

Is GHSA-QC22-QWM9-J8RX exploitable, and should I be worried?

Whether GHSA-QC22-QWM9-J8RX is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether GHSA-QC22-QWM9-J8RX is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

GHSA-QC22-QWM9-J8RX in npm-groovy-lint

Q: Which versions of npm-groovy-lint are affected by GHSA-QC22-QWM9-J8RX?

npm-groovy-lint (npm) versions < 9.1.0 is affected.

Q: Is there a fix for GHSA-QC22-QWM9-J8RX?

Yes. GHSA-QC22-QWM9-J8RX is fixed in 9.1.0. Upgrade to this version or later.

Q: Is GHSA-QC22-QWM9-J8RX exploitable, and should I be worried?

Whether GHSA-QC22-QWM9-J8RX is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether GHSA-QC22-QWM9-J8RX is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix GHSA-QC22-QWM9-J8RX?

Upgrade npm-groovy-lint to 9.1.0 or later.

Summary

Remote Code Execution in npm-groovy-lint

Versions of npm-groovy-lint prior to 9.1.0 bundle vulnerable versions of the Log4j library which are subject to remote code execution via jndi rendering. As a result npm-groovy-lint prior to 9.1.0 is also vulnerable.

Impact

The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths. Typical impact: varies by context: data corruption, logic bypass, or denial of service.

Affected versions

npm-groovy-lint (< 9.1.0)

Security releases

npm-groovy-lint → 9.1.0 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade npm-groovy-lint to 9.1.0 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is GHSA-QC22-QWM9-J8RX? GHSA-QC22-QWM9-J8RX is a critical-severity improper input validation vulnerability in npm-groovy-lint (npm), affecting versions < 9.1.0. It is fixed in 9.1.0. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.
Which versions of npm-groovy-lint are affected by GHSA-QC22-QWM9-J8RX? npm-groovy-lint (npm) versions < 9.1.0 is affected.
Is there a fix for GHSA-QC22-QWM9-J8RX? Yes. GHSA-QC22-QWM9-J8RX is fixed in 9.1.0. Upgrade to this version or later.
Is GHSA-QC22-QWM9-J8RX exploitable, and should I be worried? Whether GHSA-QC22-QWM9-J8RX is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether GHSA-QC22-QWM9-J8RX is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix GHSA-QC22-QWM9-J8RX? Upgrade npm-groovy-lint to 9.1.0 or later.