How severe is GHSA-cp47-r258-q626?

No CVSS score has been assigned to GHSA-cp47-r258-q626 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-cp47-r258-q626?

GHSA-cp47-r258-q626 affects the following packages: vega (npm), vega (npm). Ecosystems affected: npm.

How do I fix GHSA-cp47-r258-q626?

Update vega to 5.4.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cp47-r258-q626 is resolved across your whole dependency graph.

How do I detect GHSA-cp47-r258-q626 in my npm dependencies?

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

How do I mitigate GHSA-cp47-r258-q626 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-cp47-r258-q626?

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

Is GHSA-cp47-r258-q626 actively exploited in the wild?

No public exploit code has been indexed for GHSA-cp47-r258-q626 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-cp47-r258-q626 published, and has it been updated?

GHSA-cp47-r258-q626 was published on March 2, 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

GHSA-cp47-r258-q626 — vega

Fix: vega/vega#1892

GHSA-cp47-r258-q626 is a remote code execution vulnerability in vega. A fix is available for vega — see the affected versions and patch details below.

Vega vulnerable to arbitrary code execution when clicking href links

Published

Mar 2, 2023

Updated

Mar 2, 2023

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Mar 2, 2023 · OSV.dev, 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.

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

veganpm

689Kdownloads / week

Description

Vega is vulnerable to arbitrary code execution when clicking href links. Versions 5.4.1 and 4.5.1 contain a patch.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`vega`	≥ 5.0.0&&< 5.4.1	5.4.1`npm install vega@5.4.1`
📦npm	`vega`	all versions	4.5.1`npm install vega@4.5.1`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for vega, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update vega to 5.4.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cp47-r258-q626 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-cp47-r258-q626 can be triaged on real exposure rather than presence alone.

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

Frequently Asked Questions

Vega is vulnerable to arbitrary code execution when clicking href links. Versions 5.4.1 and 4.5.1 contain a patch.

O3 Security · Impact-Aware SCA

Is GHSA-cp47-r258-q626 in your dependencies?

O3 Security finds GHSA-cp47-r258-q626 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