How severe is GHSA-f698-m2v9-5fh3?

No CVSS score has been assigned to GHSA-f698-m2v9-5fh3 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-f698-m2v9-5fh3?

GHSA-f698-m2v9-5fh3 affects the following packages: opencv (npm). Ecosystems affected: npm.

How do I fix GHSA-f698-m2v9-5fh3?

Update opencv to 6.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f698-m2v9-5fh3 is resolved across your whole dependency graph.

How do I detect GHSA-f698-m2v9-5fh3 in my npm dependencies?

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

How do I mitigate GHSA-f698-m2v9-5fh3 if there is no patch (or I can't update yet)?

Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Is GHSA-f698-m2v9-5fh3 actively exploited in the wild?

No public exploit code has been indexed for GHSA-f698-m2v9-5fh3 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-f698-m2v9-5fh3 published, and has it been updated?

GHSA-f698-m2v9-5fh3 was published on June 4, 2019 and was last updated on August 31, 2020. 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

Command Injection in opencvGHSA-f698-m2v9-5fh3

Fix: peterbraden/node-opencv@81a4b86

GHSA-f698-m2v9-5fh3 is a remote code execution vulnerability in opencv. A fix is available for opencv — see the affected versions and patch details below.

Published

Jun 4, 2019

Updated

Aug 31, 2020

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Aug 31, 2020 · 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.

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

opencvnpm

526downloads / week

Description

Versions of opencvprior to 6.1.0 are vulnerable to Command Injection. The utils/ script find-opencv.js does not validate user input allowing attackers to execute arbitrary commands.

Recommendation

Upgrade to version 6.1.0.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`opencv`	all versions	6.1.0`npm install opencv@6.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 opencv, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update opencv to 6.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f698-m2v9-5fh3 is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Frequently Asked Questions

Versions of `opencv`prior to 6.1.0 are vulnerable to Command Injection. The utils/ script find-opencv.js does not validate user input allowing attackers to execute arbitrary commands. ## Recommendation Upgrade to version 6.1.0.

O3 Security · Impact-Aware SCA

Is GHSA-f698-m2v9-5fh3 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works