Solana fixes a vulnerability that could silently corrupt sto
On November 20, 2026, PANews and Odaily Planet Daily successively reported that Solidity released version 0.8.39, fixing a medium-severity vulnerability that could corrupt storage without reporting an error. The vulnerability occurs when a recursive struct in storage is copied into a storage struct that contains it, and multiple 0.8 versions are affected. The fix adds a runtime overlap check but increases gas consumption. After scanning verified contracts, the team found no affected deployed contracts.
Event Timeline
- [11-20 03:05] Solidity released version 0.8.39, fixing a vulnerability that could silently corrupt storage (PANews)
- [11-20 03:11] Vulnerability that could silently corrupt storage fixed, Solidity releases version 0.8.39 (Odaily Planet Daily)
Background and Impact
On November 20, 2026, PANews at 03:05 and Odaily Planet Daily at 03:11 successively reported that Solidity released version 0.8.39, fixing a medium-severity vulnerability that could corrupt storage without reporting an error. The two sources are consistent in their descriptions of the vulnerability's severity rating, trigger scenarios, and fix approach, with no discrepancy.
According to both sources, the vulnerability occurs when a recursive struct in storage is copied into a storage struct that contains it, and multiple 0.8 versions are affected. The fix is to add a runtime overlap check, at the cost of increased gas consumption. The Solidity team said after scanning verified contracts that no affected deployed contracts were found. Neither report listed the specific affected version numbers or disclosed the number of contracts covered by the scan.
In terms of impact, this is a compiler-level update. Those directly affected are developers who use the relevant 0.8 versions to compile contracts: upgrading to 0.8.39 provides the fix, but they need to assess the gas increase brought by the runtime overlap check. For deployed contracts, the team's conclusion is that no affected ones were found, and the wording of this conclusion is limited to verified contracts. For users who do not directly write contracts, this type of update will not change daily operations on platforms such as Binance registration/APP download, Gate.io registration/APP download, HTX registration/APP download, Bitget registration/APP download, and OKX registration/APP download, but the reliability of the contract toolchain remains a foundational part of on-chain application security.
Follow-up points worth watching include: further clarification of the affected version range, developer feedback on gas cost changes, and whether the team publishes a more complete scan scope. Before the official side provides more details, judgment of the vulnerability's actual scope of impact remains limited to "no affected ones found among verified contracts."
FAQ
### Will this vulnerability affect contracts I have already deployed?
According to the official statement cited by both sources, after scanning verified contracts, the team found no affected deployed contracts. The wording of this conclusion is limited to verified contracts; the reports did not disclose the scanning of unverified contracts.
### What is the cost of upgrading to 0.8.39?
The fix adds a runtime overlap check, so it increases gas consumption. Developers who use the relevant 0.8 versions to compile contracts need to assess the trade-off between getting the fix and bearing higher gas costs.
### Which versions are affected?
Both sources say multiple 0.8 versions are affected, but the reports do not list the specific affected version numbers or explain the start and end of the version range; further official clarification is needed.