Safe contract version 1.5.0 is now available in Safe{Wallet}

New Safes created in Safe{Wallet} now run on Safe contracts v1.5.0. Existing Safes on 1.3.0 or 1.4.1 can upgrade from Settings in one transaction. Safe recommends upgrading to 1.5.0 now.

Why upgrade

Version 1.5.0 has been live onchain since 3 July 2025. It is the current version of the Safe contracts, and the one new security features will build on.

For every Safe, failed transactions now return the underlying error instead of a generic revert. Signature validation moves to current ERC-1271.

For Safes that run modules, a Module Guard now checks every module transaction against the same rules as your other transactions. Modules can no longer bypass guards.

The full change list is in the contracts team's announcement, Introducing Safe v1.5.0.

What remains the same

Your address, owners, threshold, guards, and modules carry over. Signers approve the upgrade like any other transaction.

What to check before upgrading

• If your Safe is owned by other Safes

Owner Safes on 1.3.0 and 1.4.1 are not affected. They keep signing as they do today.

• If your Safe is owned by another smart contract(not Safes 1.3.0 or above)

Version 1.5.0 checks contract signatures more strictly. The owner contract must implement isValidSignature(bytes32, bytes) and return the ERC-1271 value in the exact format the standard specifies. Some contracts return a response that earlier Safe versions accepted and 1.5.0 does not. If that owner is needed to reach your threshold, confirm it before upgrading. Otherwise the Safe cannot execute after the upgrade.

How to check if your owner Safes (as signers) are compatible

• Go to Settings → Owners.

• Most Safes are not affected. If every owner is a wallet address, another Safe, or both, upgrade as normal.

• If one of your owners is another kind of smart contract, confirm with its provider that the contract implements isValidSignature(bytes32, bytes) and returns the ERC-1271 value in the exact format the standard defines.

• Do not upgrade until you have that confirmation. If that owner is needed to reach your threshold and it cannot produce a valid signature, your Safe cannot execute transactions.

How to upgrade

Open your Safe. Go to Settings, then Contract version. Create the upgrade transaction, collect signatures, execute. Safes on several networks upgrade per network.

Safe{Wallet}

22 September 2026

Copy link