RUSTSEC-2020-0029: Allows viewing and modifying arbitrary structs as bytes

What to do

1. See which version you have: cargo tree -i rgb (it also shows which of your dependencies pulls it in).
2. Update within your version requirement: cargo update -p rgb. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for example rgb = "0.8.20") or update the dependency that pulls it in.
3. Check again with cargo audit, or paste your Cargo.lock into our Cargo.toml checker.

Details from the advisory

Affected versions of rgb crate allow viewing and modifying data of any type T wrapped in RGB<T> as bytes, and do not correctly constrain RGB<T> and other wrapper structures to the types for which it is safe to do so.

Safety violation possible for a type wrapped in RGB<T> and similar wrapper structures:

• If T contains padding, viewing it as bytes may lead to exposure of contents of uninitialized memory.
• If T contains a pointer, modifying it as bytes may lead to dereferencing of arbitrary pointers.
• Any safety and/or validity invariants for T may be violated.

The issue was resolved by requiring all types wrapped in structures provided by RGB crate to implement an unsafe marker trait.

References

• Package: crates.io/crates/rgb
• Advisory: rustsec.org/advisories/RUSTSEC-2020-0029.html
• Report: github.com/kornelski/rust-rgb/issues/35

From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.