Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🦀 crates.io

GHSA-8r76-fr72-j32w

GHSA-8r76-fr72-j32w is a security vulnerability in mpl-bubblegum. O3 Security confirms whether GHSA-8r76-fr72-j32w is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Creator Verification Error when Bubblegum Activate

Published
Dec 12, 2022
Updated
Dec 12, 2022
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed

Blast Radius

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
EcosystemPackageVulnerable rangeFix
🦀crates.iompl-bubblegumall versions0.6.0
🦀crates.iompl-token-metadata1.5.0&&< 1.6.31.6.3

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mpl-bubblegum. 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.

  2. 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.

  3. 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.

  4. How O3 protects you

    O3 pinpoints whether GHSA-8r76-fr72-j32w 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-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 detects GHSA-8r76-fr72-j32w across crates.io dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.