# GHSA-8r76-fr72-j32w: Creator Verification Error when Bubblegum Activate

> Attackers can bypass creator verification in Bubblegum by exploiting a Token Metadata provision, allowing unauthorized verification of creators.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Dec 2022

## What is GHSA-8r76-fr72-j32w?

GHSA-8r76-fr72-j32w is a vulnerability in mpl-bubblegum, published on 12 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

This was an error found by @metamania01 of the Audit Company Solshield.

It allowed one to verify a creator that did not sign by making use of a provision in Token Metadata that allows Creators who have signed compressed nfts to allow them to decompress with verified creators.

The issue is now patched.
For more info see.
https://twitter.com/thehasheddude/status/1601642138143375360

## Which versions are affected by GHSA-8r76-fr72-j32w?

4 open source packages ship an affected version, including mpl-bubblegum and mpl-token-metadata.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mpl-bubblegum` | crates.io | All versions | 0.6.0 |
| `mpl-bubblegum` | crates.io | All versions | 0.6.0 |
| `mpl-token-metadata` | crates.io | From 1.5.0 | 1.6.3 |
| `mpl-token-metadata` | crates.io | From 1.5.0 | 1.6.3 |

## How do I fix GHSA-8r76-fr72-j32w?

Upgrade mpl-bubblegum to 0.6.0 or later.

## Is GHSA-8r76-fr72-j32w being exploited?

There is no known exploitation of GHSA-8r76-fr72-j32w in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-8r76-fr72-j32w and fix it if it is affected.

What it is: GHSA-8r76-fr72-j32w is a vulnerability in mpl-bubblegum, published on 12 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-8r76-fr72-j32w in the wild and no public exploit code.

Affected packages and fixed versions:
- mpl-bubblegum (crates.io): affected all versions; fixed in 0.6.0
- mpl-bubblegum (crates.io): affected all versions; fixed in 0.6.0
- mpl-token-metadata (crates.io): affected from 1.5.0; fixed in 1.6.3
- mpl-token-metadata (crates.io): affected from 1.5.0; fixed in 1.6.3

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-8r76-fr72-j32w/ (Markdown: https://insights.sbomify.com/GHSA-8r76-fr72-j32w/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-8r76-fr72-j32w

---
From sbomify Insights: https://insights.sbomify.com/GHSA-8r76-fr72-j32w/
Summaries are generated and may contain mistakes; the official description above is the record.