Flare go-flare v1.15.1 emergency hard fork
Flare Network is activating the mandatory go-flare v1.15.1 hard fork on 18 November 2026 at 14:00 UTC, bringing the update forward after an attempted exploit of a bug was detected. The upgrade concerns the network behind the FLR token and is aimed at validators and node operators.
What is happening
Flare's monitoring systems detected an attempt to exploit a bug in the node software. The go-flare v1.15.1 release is a hard fork that patches a weakness in upstream code on which Flare's nodes run. The fix had originally been planned for later in the month, but the project moved the date forward after spotting someone trying to use the vulnerability.
Validators and node operators are urged to upgrade to the new version before the activation time. Nodes that do not upgrade risk falling out of step with the network once the fork goes live, which is the usual consequence of a mandatory hard fork. Flare states that user funds and keys are not affected, and ordinary users do not need to take any action.
go-flare is the node software that runs the Flare and Songbird networks. According to the project's GitHub repository, it is a modified version of avalanchego and coreth that incorporates the Flare Time Series Oracle (FTSO) and State Connector, so fixes in the upstream Avalanche codebase can be relevant to Flare's own nodes. Flare has not published further technical detail on the weakness in the sources reviewed, and operators are directed to the official go-flare release notes for upgrade instructions.
Why it matters
Mandatory node upgrades are a regular part of the network's operation; earlier releases such as go-flare v1.12.0 in November 2025 also required all node operators to upgrade before activation dates. What sets v1.15.1 apart is that it was accelerated in response to a detected exploit attempt rather than following a pre-announced schedule, which leaves operators a short window to prepare.
Validators take part in consensus voting and are selected as block proposers, weighted by their total stake, so keeping them on the same software version matters when a protocol-level fix is deployed. For FLR holders, the main points are that funds and keys are reported as unaffected and that no action is required from them. Those who delegate or run infrastructure may want to confirm that their validator or provider has upgraded in time.
Key details
- Date: 18 November 2026, 14:00 UTC
- Project: Flare Network
- Coins: FLR
- Category: Network Upgrade
- Status: Confirmed
- Source: https://cryptonews.net/news/altcoins/33733584/
Cambodia
UK