How severe is GHSA-v2mw-5mch-w8c5?

No CVSS score has been assigned to GHSA-v2mw-5mch-w8c5 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-v2mw-5mch-w8c5?

GHSA-v2mw-5mch-w8c5 affects the following packages: canvg (npm), canvg (npm). Ecosystems affected: npm.

How do I fix GHSA-v2mw-5mch-w8c5?

Update canvg to 4.0.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v2mw-5mch-w8c5 is resolved across your whole dependency graph.

How do I detect GHSA-v2mw-5mch-w8c5 in my npm dependencies?

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

How do I mitigate GHSA-v2mw-5mch-w8c5 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.

Is GHSA-v2mw-5mch-w8c5 actively exploited in the wild?

No public exploit code has been indexed for GHSA-v2mw-5mch-w8c5 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-v2mw-5mch-w8c5?

GHSA-v2mw-5mch-w8c5 has an EPSS (Exploit Prediction Scoring System) score of 0.7%, placing it in the 54th 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-v2mw-5mch-w8c5?

GHSA-v2mw-5mch-w8c5 is classified as CWE-1321 (CWE-1321). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-v2mw-5mch-w8c5 published, and has it been updated?

GHSA-v2mw-5mch-w8c5 was published on March 10, 2025 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

canvg Prototype Pollution vulnerabilityGHSA-v2mw-5mch-w8c5

Fix: canvg/canvg@c3743e6

GHSA-v2mw-5mch-w8c5 is a CWE-1321 vulnerability in canvg. A fix is available for canvg — see the affected versions and patch details below.

Also known asCVE-2025-25977

Published

Mar 10, 2025

Updated

Sep 10, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

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

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA’s SSVC triage for GHSA-v2mw-5mch-w8c5.

EPSS Exploitation Probability

via FIRST.org ↗

0.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs54th percentile — riskier than 54% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

2 pkgs 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.

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

canvgnpm

20.7Mdownloads / week

Description

An issue in canvg prior to v.4.0.3 and v3.0.11 can lead to prototype pollution via the Constructor of the class StyleElement.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`canvg`	≥ 4.0.0&&< 4.0.3	4.0.3`npm install canvg@4.0.3`
📦npm	`canvg`	all versions	3.0.11`npm install canvg@3.0.11`

Affected Products

1 product · 2 configurations

Application

canvgcanvg

≥ 4.0.0 && < 4.0.3

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for canvg, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update canvg to 4.0.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v2mw-5mch-w8c5 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.

Frequently Asked Questions

An issue in canvg prior to v.4.0.3 and v3.0.11 can lead to prototype pollution via the Constructor of the class StyleElement.

O3 Security · Impact-Aware SCA

Is GHSA-v2mw-5mch-w8c5 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works