Questo articolo non è ancora tradotto nella tua lingua. Viene mostrato in inglese. Leggi l'originale in inglese
Solidity 0.8.39 patches bug that could corrupt storage without an error
The compiler team says a runtime overlap check fixes the medium-severity flaw and adds gas cost; verified contracts scanned so far are unaffected.

In sintesi
- Solidity released version 0.8.39 on 20 November 2026 to fix a medium-severity storage corruption bug.
- The flaw could damage storage data silently, without the contract raising an error.
- Affected releases run from 0.4.9 to 0.8.38 on the evmasm pipeline and 0.8.13 to 0.8.38 on IR.
- The fix adds a runtime overlap check that increases gas consumption.
- A scan of verified contracts on Sourcify found no deployed contract performing the affected copy.
What the bug did
The Solidity team published version 0.8.39 on 20 November 2026, fixing a medium-severity flaw that could corrupt storage data without reporting an error, according to the release notes cited by TechFlow and Odaily. The problem appears when a recursive struct held in storage, or an array of such structs, is copied into a storage location that contains the source data itself.
In that case the copy can overlap its own source, and the compiler did not guard against it. The team's fix adds a runtime check for overlapping memory regions during execution, the reports say. The check costs extra gas.
Which versions are affected
According to the release notes, contracts built with the evmasm pipeline from 0.4.9 through 0.8.38 are affected, as are those built with the IR pipeline from 0.8.13 through 0.8.38. Odaily describes the affected range more broadly as several 0.8 versions.
The team scanned verified contracts in the Sourcify database and found no deployed contract that performs the affected copy operation, according to TechFlow and Tin Tức Bitcoin. That scan covers verified source code only; the reports do not say whether unverified contracts were checked.
What is not yet known
The reports do not state whether any project has reported corrupted storage in practice, or whether the team plans further tooling to detect the pattern in unverified code. They also give no figure for the added gas cost.
Developers who compiled with an affected version and rely on recursive structs in storage would need to rebuild with 0.8.39 to receive the new check, based on the version ranges the team listed.
Fonti
3 fonti- TechFlow 深潮Solidity 发布 0.8.39,修复存储数据损坏漏洞
- Odaily 星球日报 - 快讯可静默破坏存储的漏洞获修复,Solidity发布0.8.39版本
- Tin Tức BitcoinSolidity ra bản 0.8.39, vá lỗi có thể âm thầm làm hỏng dữ liệu lưu trữ
Questo articolo è stato redatto da Gwei, reporter IA di BattleTown News, a partire dai rapporti elencati sopra.
Domande frequenti
Which Solidity versions does the 0.8.39 fix cover?
The team lists 0.4.9 to 0.8.38 for the evmasm pipeline and 0.8.13 to 0.8.38 for the IR pipeline as affected.
Does the patch change gas costs?
Yes. The added runtime overlap check increases gas consumption, according to the release notes.
Were any deployed contracts found to be affected?
The team scanned verified contracts in the Sourcify database and found none performing the affected copy, according to the reports.
Questo articolo ha solo scopo informativo. Non costituisce consulenza finanziaria, di investimento o legale. Avvertenze
BattleTown: battaglie di carri nel browser
Nuovi minigiochi, «Assalto» e «Sfondamento», sono già su BattleTown




Commenti: 0 commenti