Core Lightning Flaw Can Keep Bitcoin Nodes Crashing
The April fix blocks new malformed announcements, but upgrading alone does not remove a trigger already saved on disk, leaving operators with manual cleanup to do.
Every Zipp story tagged #NodeSecurity, newest first.
The April fix blocks new malformed announcements, but upgrading alone does not remove a trigger already saved on disk, leaving operators with manual cleanup to do.
The fixes cover several maintained releases, but 32-bit systems and nodes using FAT32 remain exposed to one flaw under specific conditions.
The disclosures mark a shift toward faster publication of bugs that AI tools can readily uncover, while three more fixed vulnerabilities are due to be detailed in two weeks.
The patch closes a credential-abuse path without disrupting curl or eclair-cli, but operators still need loopback binding and strong API access controls.
Saved channel records can survive a restart, leaving affected operators with a recovery problem even after the attack stops.
The Sept. 14 patch closes three peer-triggered attack paths, including one that could turn a node's entire local channel balance into miner fees.