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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

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 pinpoints whether GHSA-cp47-r258-q626 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

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

GHSA-cp47-r258-q626

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

Blast Radius

2 pkgs affected

📦vega📦vega

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

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	`vega`	all versions	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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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 pinpoints whether GHSA-cp47-r258-q626 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

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 detects GHSA-cp47-r258-q626 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works