How severe is GHSA-665w-mwrr-77q3?

GHSA-665w-mwrr-77q3 has a CVSS score of 5.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-665w-mwrr-77q3?

GHSA-665w-mwrr-77q3 affects the following packages: @jmondi/url-to-png (npm). Ecosystems affected: npm.

How do I fix GHSA-665w-mwrr-77q3?

Update @jmondi/url-to-png to 2.0.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-665w-mwrr-77q3 is resolved across your whole dependency graph.

How do I detect GHSA-665w-mwrr-77q3 in my npm dependencies?

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

How do I mitigate GHSA-665w-mwrr-77q3 if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is GHSA-665w-mwrr-77q3 actively exploited in the wild?

No public exploit code has been indexed for GHSA-665w-mwrr-77q3 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.

What is the EPSS score for GHSA-665w-mwrr-77q3?

GHSA-665w-mwrr-77q3 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 45th 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.

What type of vulnerability is GHSA-665w-mwrr-77q3?

GHSA-665w-mwrr-77q3 is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-665w-mwrr-77q3 published, and has it been updated?

GHSA-665w-mwrr-77q3 was published on June 5, 2024 and was last updated on September 10, 2026. 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

MEDIUM severity

Arbitrary file read via Playwright's screenshot feature exploiting file wrapperGHSA-665w-mwrr-77q3

MEDIUMFix: jasonraimondi/url-to-png@9336020

GHSA-665w-mwrr-77q3 is a medium-severity (CVSS 5.3) Path Traversal vulnerability in @jmondi/url-to-png. A fix is available for @jmondi/url-to-png — see the affected versions and patch details below.

Also known asCVE-2024-37169

Published

Jun 5, 2024

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-665w-mwrr-77q3.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs45th percentile — riskier than 45% 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

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.

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

@jmondi/url-to-pngnpm

25downloads / week

Description

Impact

All users of url-to-png. Please see https://github.com/jasonraimondi/url-to-png/issues/47

Patches

v2.0.3 requires input url to be of protocol http or https

Workarounds

Requires upgrade.

References

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@jmondi/url-to-png`	all versions	2.0.3`npm install @jmondi/url-to-png@2.0.3`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @jmondi/url-to-png, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @jmondi/url-to-png to 2.0.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-665w-mwrr-77q3 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Frequently Asked Questions

### Impact All users of url-to-png. Please see https://github.com/jasonraimondi/url-to-png/issues/47 ### Patches [v2.0.3](https://github.com/jasonraimondi/url-to-png/releases/tag/v2.0.3) requires input url to be of protocol `http` or `https` ### Workarounds Requires upgrade. ### References - https://github.com/jasonraimondi/url-to-png/issues/47 - https://github.com/user-attachments/files/15536336/Arbitrary.File.Read.via.Playwright.s.Screenshot.Feature.Exploiting.File.Wrapper.pdf