Home / Smart Contract Auditing / Solidity Compiler Releases Versions 0.8.32 and 0.8.33 with Crucial Bug Fixes and Infrastructure Migration

Solidity Compiler Releases Versions 0.8.32 and 0.8.33 with Crucial Bug Fixes and Infrastructure Migration

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 versions 0.8.32 and 0.8.33 of the Solidity Compiler. These consecutive updates arrive to address a combination of critical low-severity bug fixes, long-standing developer experience hurdles, and an unexpected backwards-incompatible issue introduced during the initial rollout. Alongside these technical patches, the release marks a major operational shift regarding how historical compiler binaries are hosted and distributed to the global Web3 development community.

The primary release in this rollout, version 0.8.32, was initially conceptualized as a standard maintenance update designed to patch an important low-severity bug while simultaneously resolving a persistent issue that had previously hampered the ability of developers to use modules as clean namespaces for custom events and error types. However, shortly after version 0.8.32 was tagged and published, the team discovered an unintentional backwards-incompatible change that prompted the rapid formulation and deployment of a hotfix release designated as version 0.8.33.

Important Bugfixes

The most prominent technical focus of the 0.8.32 release centers around a vulnerability known as the "Lost Storage Array Write On Slot Overflow." This critical issue, which affects operations involving the clearing of or copying from arrays that straddle the absolute end of storage, was formally reported to the development team by security researcher @Audittens. Following the report, the engineering team prioritized a comprehensive fix to ensure data integrity across complex contract storage layouts.

According to the core engineering team, this particular bug manifests only under very specific and unusual circumstances. It typically impacts smart contracts that employ highly unconventional storage layouts designed intentionally to bypass the compiler’s built-in safeguards. These safeguards normally prevent developers from introducing state variables that extend beyond the maximum allocated boundary of contract storage. Bypassing these protective measures is generally only possible through the deliberate use of inline assembly or by declaring dynamic data types of such immense size that the underlying data area crosses the storage overflow boundary.

Historical analysis of the codebase revealed that this bug has existed since the very first iteration of the compiler, tracing all the way back to version v0.1.0. Furthermore, the development team confirmed that both standard compilation pipelines are affected, and the presence or absence of the optimizer has no bearing on whether a contract is vulnerable. To help developers thoroughly understand the technical implications of this issue, the team published a dedicated companion blog post detailing how the bug was originally introduced, identifying the specific patterns of smart contracts that could theoretically be affected, and outlining the exact consequences of the storage overflow.

Other Notable Changes

Beyond critical bug remediation, the new compiler versions introduce notable improvements aimed at enhancing developer ergonomics and streamlining project architecture. Among these is a fix for emitting events and reverting with errors via module member access. In previous versions of the compiler, developers attempting to emit an event or revert with a custom error referenced through an imported module would encounter an internal compiler error, bringing the build process to an abrupt halt.

With the release of version 0.8.32, this limitation has been completely removed. Code structures that import a module containing custom errors or events and access them via member notation now compile seamlessly without throwing internal errors. This update represents another crucial milestone in the ongoing initiative to achieve complete feature parity between free functions and traditional libraries within the Solidity ecosystem. Definitions housed inside modern source file modules are widely promoted by the core team as the preferred, modern alternative to organizing and namespacing code through libraries.

In tandem with these language-level enhancements, the project has executed a significant infrastructure migration concerning the hosting of historical release binaries. The solc-bin repository, which maintains historical versions of the compiler, has been officially migrated from Amazon Web Services Simple Storage Service (AWS S3) to Cloudflare R2. This structural move was undertaken as part of an ongoing initiative to optimize operational costs and streamline resource management.

For the vast majority of developers and automated CI/CD pipelines, this transition is entirely transparent. Static binaries remain fully accessible at their traditional location on binaries.soliditylang.org, and the underlying filesystem structure has been preserved without modification. However, the migration temporarily impacted the availability of the legacy solc-bin.ethereum.org domain. While that legacy domain remains functional under temporary support arrangements, the Solidity team is officially deprecating it due to a lack of direct control over the domain. Development teams and maintainers of third-party tooling whose scripts still rely on the legacy endpoint are strongly advised to update their configurations to point directly to binaries.soliditylang.org.

Hotfix Release

The deployment of version 0.8.32, while successful in resolving longstanding storage array and module accessibility hurdles, unintentionally introduced a separate complication. Shortly after the release package was finalized, developers discovered that version 0.8.32 triggered an internal compiler error whenever code attempted to reference or call getter functions automatically generated for constant state variables.

While this specific defect did not pose a security vulnerability and could not result in dangerous miscompilations or corrupted contract logic, it effectively blocked standard compilation for developers utilizing common coding patterns. Recognizing that the affected pattern is widespread across existing codebases, the core team acted swiftly to formulate version 0.8.33 as an immediate hotfix.

The introduction of 0.8.33 rectifies the internal compiler error regarding constant state variable getters. Consequently, while version 0.8.32 remains functionally safe in terms of output execution, the development team strongly recommends that the community bypass 0.8.32 entirely and upgrade directly to version 0.8.33 to ensure uninterrupted development workflows.

Full Changelog

The dual release schedule encompasses a focused set of adjustments across both versions. Version 0.8.32 established the foundation by patching the longstanding storage array overflow vulnerability and resolving the module member access bug for events and errors, alongside the underlying AWS-to-Cloudflare infrastructure transition for compiler binaries. Version 0.8.33 immediately followed up as a dedicated bugfix release focused entirely on eliminating the internal compiler error associated with constant state variable getter functions.

How to Install and Upgrade

Developers seeking to update their development environments to the latest iteration of the Solidity Compiler can consult the comprehensive installation documentation provided on the official Solidity portal. Release packages and pre-compiled binaries for version 0.8.33 are available for direct download through the official GitHub repository.

For teams preferring to compile the software from source code, project maintainers emphasize a critical precaution: developers must avoid utilizing the raw source archives generated automatically by the GitHub interface. Instead, builds should be compiled using the official solidity_0.8.33.tar.gz source tarball provided within the release assets to ensure proper dependency management and build integrity.

The Solidity core team extended formal recognition and gratitude to the community members and security researchers whose ongoing contributions, rigorous testing, and prompt reporting continue to secure the compiler ecosystem.

Tagged: