using tx.origin in access control checks

[joanthecoder]

Is using tx.origin in access control checks still considered a security risk in EVM smart contracts? I’m reading old posts saying to avoid it but wanted to confirm if that’s still true today.

[marceontech]

Yes, it's still considered a serious security risk.
Using tx.origin in access control is unsafe because any contract that your user interacts with can trigger your contract, meaning that malicious contracts could trick users into executing actions as if they were authorized.

The correct approach is to use msg.sender, which refers to the direct caller of the function, not the origin of the full transaction.

Best practice: never use tx.origin for authorization logic, this hasn't changed.