How severe is GHSA-4vjr-crvh-383h?

GHSA-4vjr-crvh-383h has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-4vjr-crvh-383h?

GHSA-4vjr-crvh-383h affects the following packages: @napi-rs/image (npm). Ecosystems affected: npm.

How do I fix GHSA-4vjr-crvh-383h?

Update @napi-rs/image to 1.7.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4vjr-crvh-383h is resolved across your whole dependency graph.

How do I detect GHSA-4vjr-crvh-383h in my npm dependencies?

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

How do I mitigate GHSA-4vjr-crvh-383h 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-4vjr-crvh-383h?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-4vjr-crvh-383h can be triaged on real exposure rather than presence alone.

Is GHSA-4vjr-crvh-383h actively exploited in the wild?

No public exploit code has been indexed for GHSA-4vjr-crvh-383h 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-4vjr-crvh-383h published, and has it been updated?

GHSA-4vjr-crvh-383h was published on September 27, 2023. 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

HIGH severity

GHSA-4vjr-crvh-383h — @napi-rs/image

HIGHFix: Brooooooklyn/Image@aa07979

GHSA-4vjr-crvh-383h is a high-severity (CVSS 8.8) remote code execution vulnerability in @napi-rs/image. A fix is available for @napi-rs/image — see the affected versions and patch details below.

@napi-rs/image affected by libwebp CVE

Published

Sep 27, 2023

Updated

Sep 27, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 27, 2023 · 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.

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

@napi-rs/imagenpm

97Kdownloads / week

Description

Impact

Heap buffer overflow in libwebp allows a remote attacker to perform an out of bounds memory write via a crafted webp image.

References

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@napi-rs/image`	all versions	1.7.0`npm install @napi-rs/image@1.7.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @napi-rs/image, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @napi-rs/image to 1.7.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4vjr-crvh-383h 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-4vjr-crvh-383h can be triaged on real exposure rather than presence alone.

Tailored to GHSA-4vjr-crvh-383h. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact Heap buffer overflow in `libwebp` allows a remote attacker to perform an out of bounds memory write via a crafted webp image. ### References - https://github.com/advisories/GHSA-j7hp-h8jx-5ppr - https://blog.isosceles.com/the-webp-0day/

O3 Security · Impact-Aware SCA

Is GHSA-4vjr-crvh-383h in your dependencies?

O3 Security finds GHSA-4vjr-crvh-383h across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works