# GHSA-cp47-r258-q626: Vega vulnerable to arbitrary code execution when clicking href links

> An attacker can execute arbitrary code if a user clicks a malicious href link in a Vega visualization.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 2 Mar 2023

## What is GHSA-cp47-r258-q626?

GHSA-cp47-r258-q626 is a code injection vulnerability in vega, published on 2 Mar 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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

## Which versions are affected by GHSA-cp47-r258-q626?

4 open source packages ship an affected version, including vega.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `vega` | npm | All versions | 4.5.1 |
| `vega` | npm | All versions | 4.5.1 |
| `vega` | npm | From 5.0.0 | 5.4.1 |
| `vega` | npm | From 5.0.0 | 5.4.1 |

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

Upgrade vega to a fixed version for your release line: 4.5.1 or 5.4.1.

## Is GHSA-cp47-r258-q626 being exploited?

There is no known exploitation of GHSA-cp47-r258-q626 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-cp47-r258-q626 and fix it if it is affected.

What it is: GHSA-cp47-r258-q626 is a code injection vulnerability in vega, published on 2 Mar 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of GHSA-cp47-r258-q626 in the wild and no public exploit code.

Affected packages and fixed versions:
- vega (npm): affected all versions; fixed in 4.5.1
- vega (npm): affected all versions; fixed in 4.5.1
- vega (npm): affected from 5.0.0; fixed in 5.4.1
- vega (npm): affected from 5.0.0; fixed in 5.4.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-cp47-r258-q626/ (Markdown: https://insights.sbomify.com/GHSA-cp47-r258-q626/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-cp47-r258-q626

---
From sbomify Insights: https://insights.sbomify.com/GHSA-cp47-r258-q626/
Summaries are generated and may contain mistakes; the official description above is the record.