Skip to the rundown
GetYourBrief
Search

Rundown · Friday, October 16, 2026

Cyber news on October 16, 2026

On Friday, October 16, 2026 the Cybersecurity desk recorded 4 news events. The earliest report came from bleepingcomputer.com at 07:37 UTC.

  1. 01

    BAE Systems incident takes down US bankruptcy court notice platform

    2 outlets · first: bleepingcomputer.com Security

    Machine summary A security incident affecting BAE Systems infrastructure has disabled the Bankruptcy Noticing Center, the nationwide notice platform BAE runs for the federal judiciary, along with the National Creditor Registration Service and BNC web properties. BAE said the incident is isolated to the BNC system and that it is investigating and working to restore operations.

    1. A SecurityWeek report dated October 16 says federal bankruptcy courts have failed for roughly one week to push notices out via the Bankruptcy Noticing Center.
    2. The Administrative Office said all access to BNC systems and sites BAE operates for the judiciary is unavailable, listing bnc.uscourts.gov, bankruptcynotices.uscourts.gov, notices.uscourts.gov and the National Creditor Registration Service.
    3. With the National Creditor Registration Service offline, electronic filing system users cannot generate the creditor mailing lists used to serve documents, SecurityWeek reported.
    4. Several bankruptcy courts posted notices on October 13 describing a service disruption or interruption, and none mentioned a cybersecurity incident, SecurityWeek reported.
    5. Neither the judiciary nor BAE has disclosed the cause, whether the event was a cyberattack, or whether any data was compromised, according to SecurityWeek.

    Reported by bleepingcomputer.com and securityweek.com.

    • BAE Systems
    • SecurityWeek
    • Bankruptcy Noticing Center
    • National Creditor Registration Service
    • US Bankruptcy Courts
  2. 02

    Coverage recordwtae.com: “Cyberattack disrupts European supermarkets”

    2 outlets · first: wtae.com Threat intelligence

    Reports ran between 09:30 and 16:00 UTC on Oct 16.

    The outlets that reported this event are listed with links to their reports; no summary of ours passed our automated checks for it, which says nothing about the event (how they work).

    Reported by wtae.com and aa.com.tr.

  3. 03

    Anthropic says Claude traced NIST curve seeds in under 30 minutes

    2 outlets · first: Anthropic Security

    Machine summary Anthropic published an account stating that an internal research model determined how the seed parameters behind the NIST elliptic curves in FIPS 186-2 were generated. The company's write-up said the derivation amounts to timestamps, while Unite.AI reported the seeds traced to a 1990s random number generator. Anthropic said no changes to curve usage follow from the finding.

    1. In 2000, ECDSA was adopted by NIST within the FIPS 186-2 Digital Signature Standard; that standard releases elliptic curves in which the coefficient b comes from the hash value of a seed parameter.
    2. The NIST P-256 curve seed is listed as SEED = C49D3608 86E70493 6A6678E1 139D26B7 819F7E90, with no published derivation, according to Anthropic's research write-up
    3. Anthropic states the seeds were supplied by the NSA with no explanation or justification provided at the time
    4. In October 2026 an Anthropic employee asked an internal research model to determine how the seeds were generated without offering the known clue, and the company says Claude produced the answer in under half an hour
    5. Anthropic's write-up summarises the result as "It's just timestamps"; Unite.AI reported the same announcement as tracing the seeds to a 1990s random number generator

    Reported by Anthropic and Unite.AI.

  4. 04

    OpenBSD root exploit chains 37-year-old shared-memory kernel bug

    2 outlets · first: calif.io Vulnerability

    Machine summary The company says a fork-driven integer overflow could produce a use-after-free via a race condition, which chained with a separate out-of-bounds write allowed local privilege escalation to root. OpenBSD addressed the issues in errata 026 and errata 018, according to the write-up.

    1. A write-up from Calif states that the counter for shared memory attachments was defined in the earliest BSD sources as a signed 16-bit short, a history it dates to about 37 years.
    2. Calif indicated that when a process sharing memory attachment records is forked again and again, the counter might exceed its 32,767 limit and wrap around to become negative.
    3. Calif states the integer overflow could produce a use-after-free via a race condition, which chained with a separate kernel out-of-bounds write to allow local privilege escalation to root.
    4. The write-up says both issues were addressed by OpenBSD in errata 026 and errata 018.
    5. Calif describes the exploit as a write-what-where primitive where the write comes from a TAILQ_REMOVE operation and the destination is a predictable kernel pointer.

    Reported by calif.io and The Hacker News.

    • The Hacker News
    • Calif
    • TAILQ_REMOVE
    • BSD
    • OpenBSD
    • KARL (Kernel Address Randomized Link)

Each summary and its key facts are a machine summary of the reports linked under it; the outlets, times and counts come from those reports' own records. How a rundown is built.

Also covered for this desk

3 events homed on another desk that the Cybersecurity desk also carried on October 16, 2026.

  1. Oct 16 · AI India says evaluation-stage AI agents reached live systems uninvited 2

The days around it

Sources: the outlets' reports linked on this page; counts and times from GetYourBrief's record of those reports (methodology).