How severe is GHSA-8r76-fr72-j32w?

No CVSS score has been assigned to GHSA-8r76-fr72-j32w yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-8r76-fr72-j32w?

GHSA-8r76-fr72-j32w affects the following packages: mpl-bubblegum (crates.io), mpl-token-metadata (crates.io). Ecosystems affected: crates.io.

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

Update mpl-bubblegum to 0.6.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8r76-fr72-j32w is resolved across your whole dependency graph.

How do I detect GHSA-8r76-fr72-j32w in my crates.io dependencies?

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

How do I mitigate GHSA-8r76-fr72-j32w 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-8r76-fr72-j32w?

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

Is GHSA-8r76-fr72-j32w actively exploited in the wild?

No public exploit code has been indexed for GHSA-8r76-fr72-j32w 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-8r76-fr72-j32w published, and has it been updated?

GHSA-8r76-fr72-j32w was published on December 12, 2022. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🦀 crates.io

Not in CISA KEV

GHSA-8r76-fr72-j32w — mpl-bubblegum

Fix: metaplex-foundation/metaplex-program-library@c18591a

GHSA-8r76-fr72-j32w is a security vulnerability in mpl-bubblegum. A fix is available for mpl-bubblegum — see the affected versions and patch details below.

Creator Verification Error when Bubblegum Activate

Published

Dec 12, 2022

Updated

Dec 12, 2022

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Dec 12, 2022 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected

🦀mpl-bubblegum🦀mpl-token-metadata

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

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

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`mpl-bubblegum`	all versions	0.6.0`cargo update -p mpl-bubblegum --precise 0.6.0`
🦀crates.io	`mpl-token-metadata`	≥ 1.5.0&&< 1.6.3	1.6.3`cargo update -p mpl-token-metadata --precise 1.6.3`

Detection & mitigation playbook

Open-source dependency

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

Tailored to GHSA-8r76-fr72-j32w. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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

O3 Security · Impact-Aware SCA

Is GHSA-8r76-fr72-j32w in your dependencies?

O3 Security finds GHSA-8r76-fr72-j32w across crates.io 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