rewindex

ChangesNorthflankSecurity incident

Northflank: Incident silently edited: Security incident

Silent editDownplayed?Not classified yetChanged status.northflank.com (opens in new tab)
Summary

Summary pending. The diff below shows exactly what changed.

Downplayed?

Vendor rated this unknown; a Hacker News thread about it drew 477 points and 361 comments. Northflank Breached (opens in new tab)

This is an automated signal, not a finding. It compares the vendor’s own impact rating with public Hacker News activity (points, comments in the first hour, distinct commenters, first-hand symptom reports). HN users skew technical, so the impact on any one customer may differ. How this is computed.

Discussed on Hacker News

Threads are matched automatically by vendor name and timing; points and comments refresh every 30 minutes. Method and limits.

Incident page: the full timeline of updates

What changed

Struck in red is what Northflank removed; blue is what they added. Muted text is unchanged context.

ChangedUpdatemonitoring#1
Before: …on forward-deployed or dedicated control planes are unaffected. We have patched CVE-2026-98432 across our fleet, including BYOC…
After: …on forward-deployed or dedicated control planes are unaffected. Separately, we have patched CVE-2026-98432 across our fleet, including BYOC…

Compared with the previous archived version of this incident (10 to 30-minute polling). View the live incident (opens in new tab).

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.

How the archive is checked, and what it cannot prove.

Rewindex captured this after the last checkpoint; the next run () commits it.

History of this incident

TodayMonday, November 2Mon, Nov 2

1 rewrite, 1 incident change

Saturday, October 31

4 incident changes

Friday, October 30

1 rewrite, 4 incident changes

All Northflank changesNorthflank profileMarkdownJSON