Home / Smart Contract Auditing / Solidity v0.8.36 Released: Medium-Severity Security Fixes, SSA CFG Spilling, and EOF Backend Removal

Solidity v0.8.36 Released: Medium-Severity Security Fixes, SSA CFG Spilling, and EOF Backend Removal

The development team behind Solidity, the leading programming language for writing smart contracts on Ethereum and other blockchain networks, has officially announced the release of Solidity v0.8.36. This latest update introduces a pair of medium-severity security fixes, brings critical improvements to the experimental SSA-form code generator by adding stack-to-memory spilling, and officially removes the obsolete EVM Object Format (EOF) backend following shifts in Ethereum network upgrade roadmaps.

As smart contract security and optimization remain paramount for developers building decentralized applications, the rollout of version 0.8.36 marks another important milestone in the ongoing evolution of the compiler infrastructure. Developers are encouraged to review the release notes and begin planning their integration and testing cycles to adopt the new version safely.

Important Bugfixes

Software maintenance and rigorous security patching form the backbone of any production-grade compiler. Solidity v0.8.36 includes two specific security fixes, both classified as medium severity. While compilers translate human-readable contract logic into executable EVM bytecode, subtle edge cases can occasionally lead to unexpected compilation behavior or code generation flaws. The identification and resolution of these vulnerabilities highlight the continuous monitoring and auditing efforts carried out by the Solidity core team and external security researchers.

Although the detailed mechanics of these medium-severity fixes are embedded within the full release documentation on GitHub, their prompt resolution helps ensure that developer codebases remain protected against newly identified compilation anomalies. Routine updates like these reinforce trust in the compiler toolchain, which secures billions of dollars in decentralized finance (DeFi) protocols, non-fungible token marketplaces, and enterprise blockchain infrastructure across the globe.

Notable Features and Changes

SSA CFG Stack-to-Memory Spilling (Experimental)

One of the most significant architectural advancements in this release involves the experimental Single Static Assignment (SSA) form control-flow-graph (CFG) code generator. Introduced initially in version 0.8.35 for the Intermediate Representation (IR) pipeline, the SSA CFG generator represented a major step toward modernizing how Solidity optimizes and translates complex smart contract logic. However, one notable limitation in its initial debut was the absence of stack-to-memory spilling support.

With the release of Solidity v0.8.36, that missing capability has now been integrated into the SSA backend. Stack-to-memory spilling allows the code generator to dynamically move values from the limited EVM execution stack into memory when necessary during complex operations. In practical terms, this effectively solves the notorious "stack too deep" error for developers utilizing this backend. Complex functions involving numerous local variables, deep nesting, or intricate control flows that previously triggered compiler rejections on existing pipelines can now successfully compile through the SSA backend.

The development team emphasizes that this feature remains experimental and is not yet enabled by default for the standard --via-ir compilation pipeline. Developers wishing to test the capability must explicitly invoke it using the --experimental --via-ssa-cfg command-line flags. Stabilizing and maturing the SSA CFG code generator stands as one of the core strategic priorities for the Solidity team over the next six months, with the ultimate goal of making it robust enough for widespread production use.

Removal of the Experimental EOF Backend

Solidity v0.8.36 also brings a significant cleanup to the compiler codebase by removing the experimental EVM Object Format (EOF) backend. Substantial engineering hours and code contributions had previously been dedicated to implementing EOF support within the compiler in anticipation of its inclusion in the forthcoming Fusaka network upgrade.

However, the trajectory of Ethereum network upgrades shifted late in the development process when EOF was ultimately rejected for inclusion in the Fusaka upgrade package. Because the format lacks mainnet support and currently has no verified prospect of adoption by any operational network in the foreseeable future, the experimental backend has effectively become obsolete. To maintain a clean, maintainable, and efficient codebase, the Solidity maintainers elected to excise the dead code entirely as part of routine software housekeeping.

Full Changelog

The comprehensive release ledger for Solidity v0.8.36 encompasses a wide array of internal adjustments, ranging from specialized compiler features to targeted bugfixes designed to streamline developer workflows and enhance output reliability.

Important Bugfixes

The core engineering team has addressed several edge-case vulnerabilities and compilation bugs. These adjustments prevent potential code generation discrepancies, ensuring that smart contracts compiled under v0.8.36 behave precisely as intended according to Solidity’s strict semantics.

Compiler Features

Beyond the introduction of stack-to-memory spilling for the experimental SSA CFG backend, the compiler features category captures ongoing refinements to the IR pipeline. These enhancements are engineered to improve overall code optimization, reduce gas consumption in deployed smart contracts, and provide clearer error messaging for developers working on large-scale decentralized applications.

Bugfixes

A series of minor bugfixes have been rolled out to address parser issues, type-checking edge cases, and platform-specific compilation warnings. These refinements contribute to a smoother developer experience, minimizing friction when building and testing complex multi-contract systems.

How to Install and Upgrade

Upgrading to the latest version of the Solidity compiler is straightforward for developers utilizing standard development environments. Detailed installation instructions and environment-specific guidelines are maintained within the official documentation portal. Pre-compiled binaries and complete package archives for version 0.8.36 are publicly available through the official GitHub repository.

Teams preferring to build the compiler directly from source code are advised to avoid using the automatic source archives generated by default through GitHub’s repository interface. Instead, developers should utilize the official solidity_0.8.36.tar.gz source tarball or check out the exact v0.8.36 tag using Git to ensure all submodule dependencies and build scripts are properly configured and verified.

The core contributors and maintainers expressed their appreciation to the broader open-source community, whose ongoing bug reports, code contributions, and testing efforts remain instrumental in driving the continuous improvement and security of the Solidity ecosystem.

Tagged: