Flare Network has moved up a security update after its monitoring systems detected an attempt to exploit a bug in its node software. The update, go-flare v1.15.1, is a hard fork that fixes a weakness in upstream code used by Flare’s nodes, according to the project’s announcement shared by @FlareNetworks ($FLR).
The fix was originally scheduled for later this month. Flare moved it up after detecting an attempt to exploit the vulnerability.
Fork Activates Wednesday at 14:00 UTC
The hard fork is set to activate Wednesday at 14:00 UTC. Validators and node operators are urged to upgrade to the new version beforehand. Nodes that are not upgraded risk falling out of sync with the network after the fork activates, the usual consequence of a mandatory hard fork.
Flare says user funds and keys are unaffected. Regular users do not need to take action.
Background: How go-flare Updates Work
go-flare is the node software used to run the Flare and Songbird networks. The project’s GitHub repository describes it as a modified version of avalanchego and coreth that includes the Flare Time Series Oracle (FTSO) and State Connector. As a result, fixes to the upstream Avalanche codebase can apply to Flare’s own nodes, the kind of dependency involved in this patch.
Mandatory node upgrades are a routine part of network operations. Messari’s Flare Network update notes that earlier releases, including go-flare v1.12.0 in November 2025, required all node operators to upgrade before activation dates on Songbird and Flare. The v1.15.1 release is different because it was brought forward in response to a detected exploit attempt rather than following a schedule announced in advance.
Validators have a central role in securing the network. Flare’s developer documentation says validators participate in consensus voting and are selected as block proposers, with selection weighted by their total stake. Keeping those nodes on the same software version is therefore important when a protocol-level fix is deployed.
Flare has not provided further technical details about the weakness in the sources reviewed for this article. Node operators should consult the official go-flare release notes for upgrade instructions before Wednesday’s activation.
Sources
Source: bsc.news. Adapted by NBTC.
Add A Comment
Comments are closed.