Security context

Highlights

Auth Bypass: 3 prior fixes. Scrutinize any change in this area.

program/metaplex/tokenmeta: most-fixed (1 issue). Treat as high-risk during review.

3 high-severity fixes in this history; regressions here are high-impact.

Recurring patterns

Auth Bypass: Deserializing token accounts without enforcing that they are owned by the official Token Program allows adversaries to pass arbitrary counterfeit accounts, leading to authentication bypasses. Developers must use strict deserializers like DeserializeTokenAccount that verify account ownership.

Auth Bypass: Misconfiguring transaction accounts as read-only instead of writable prevents state changes or allows incorrect client-side simulation. Specifically, the payer account must be marked as writable when creating metadata accounts to ensure correct execution.

Auth Bypass: Logic inversion during instruction serialization (e.g., misrepresenting the presence of optional fields like the freeze authority) can lead to unexpected instruction layouts, bypass validation controls, or incorrect contract state initialization.