What is GHSA-8R76-FR72-J32W?

GHSA-8R76-FR72-J32W is a high-severity security vulnerability in mpl-bubblegum (rust), affecting versions < 0.6.0. It is fixed in 0.6.0, 1.6.3.

Which packages are affected by GHSA-8R76-FR72-J32W?

mpl-bubblegum (rust) versions = 1.5.0, < 1.6.3.

Is there a fix for GHSA-8R76-FR72-J32W?

Yes. GHSA-8R76-FR72-J32W is fixed in 0.6.0, 1.6.3. Upgrade to this version or later.

Is GHSA-8R76-FR72-J32W exploitable, and should I be worried?

Whether GHSA-8R76-FR72-J32W is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether GHSA-8R76-FR72-J32W is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

GHSA-8R76-FR72-J32W in mpl-bubblegum

Q: Which packages are affected by GHSA-8R76-FR72-J32W?

mpl-bubblegum (rust) versions = 1.5.0, < 1.6.3.

Q: Is there a fix for GHSA-8R76-FR72-J32W?

Yes. GHSA-8R76-FR72-J32W is fixed in 0.6.0, 1.6.3. Upgrade to this version or later.

Q: Is GHSA-8R76-FR72-J32W exploitable, and should I be worried?

Whether GHSA-8R76-FR72-J32W is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether GHSA-8R76-FR72-J32W is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix GHSA-8R76-FR72-J32W?

Upgrade: mpl-bubblegum to 0.6.0 or later, mpl-token-metadata to 1.6.3 or later.

Summary

Creator Verification Error when Bubblegum Activate

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

Impact

Affected versions

mpl-bubblegum (< 0.6.0) mpl-token-metadata (>= 1.5.0, < 1.6.3)

Security releases

mpl-bubblegum → 0.6.0 (rust) mpl-token-metadata → 1.6.3 (rust)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

mpl-bubblegum to 0.6.0 or later; mpl-token-metadata to 1.6.3 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is GHSA-8R76-FR72-J32W? GHSA-8R76-FR72-J32W is a high-severity security vulnerability in mpl-bubblegum (rust), affecting versions < 0.6.0. It is fixed in 0.6.0, 1.6.3.
Which packages are affected by GHSA-8R76-FR72-J32W?
- mpl-bubblegum (rust) (versions < 0.6.0)
- mpl-token-metadata (rust) (versions >= 1.5.0, < 1.6.3)
Is there a fix for GHSA-8R76-FR72-J32W? Yes. GHSA-8R76-FR72-J32W is fixed in 0.6.0, 1.6.3. Upgrade to this version or later.
Is GHSA-8R76-FR72-J32W exploitable, and should I be worried? Whether GHSA-8R76-FR72-J32W is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether GHSA-8R76-FR72-J32W is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix GHSA-8R76-FR72-J32W?
- Upgrade mpl-bubblegum to 0.6.0 or later
- Upgrade mpl-token-metadata to 1.6.3 or later