How severe is GHSA-qc22-qwm9-j8rx?

No CVSS score has been assigned to GHSA-qc22-qwm9-j8rx yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-qc22-qwm9-j8rx?

GHSA-qc22-qwm9-j8rx affects the following packages: npm-groovy-lint (npm). Ecosystems affected: npm.

How do I fix GHSA-qc22-qwm9-j8rx?

Update npm-groovy-lint to 9.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qc22-qwm9-j8rx is resolved across your whole dependency graph.

How do I detect GHSA-qc22-qwm9-j8rx in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for npm-groovy-lint. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-qc22-qwm9-j8rx if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-qc22-qwm9-j8rx?

O3 pinpoints whether GHSA-qc22-qwm9-j8rx is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-qc22-qwm9-j8rx actively exploited in the wild?

No public exploit code has been indexed for GHSA-qc22-qwm9-j8rx 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.

When was GHSA-qc22-qwm9-j8rx published, and has it been updated?

GHSA-qc22-qwm9-j8rx was published on December 20, 2021 and was last updated on December 20, 2021. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

GHSA-qc22-qwm9-j8rx

Fix: nvuillam/npm-groovy-lint#195

GHSA-qc22-qwm9-j8rx is a remote code execution vulnerability in npm-groovy-lint. O3 Security confirms whether GHSA-qc22-qwm9-j8rx is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Remote Code Execution in npm-groovy-lint

Published

Dec 20, 2021

Updated

Dec 20, 2021

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Dec 20, 2021 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

1other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

npm-groovy-lintnpm

31Kdownloads / week

Description

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`npm-groovy-lint`	all versions	9.1.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for npm-groovy-lint. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update npm-groovy-lint to 9.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qc22-qwm9-j8rx is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-qc22-qwm9-j8rx is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-qc22-qwm9-j8rx. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-qc22-qwm9-j8rx in your dependencies?

O3 detects GHSA-qc22-qwm9-j8rx across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works