LIAISON ISSUE 002 · 18 NOV 2026 · 5 MIN READ

This week one hacked AI company turned into three breaches, one of them a fake update aimed at developers. Two older flaws, in WordPress and in SSH on Alpine Linux, are still being used in attacks. Each story says what the vendor recommends and links the vendor's own notice.

HIGHAI TOOLING

One hacked AI supplier reached Notion, Uber and Cursor's users

An attacker who broke into Fireworks AI, a company that runs AI models for other businesses, took data from its customers and used one of them, Cursor, to push a fake Claude Code update to up to 5,000 developers.

Fireworks AI runs AI models for other companies. It says an attacker breached its cloud provider and reached a Fireworks development system, which gave access to some of its customers' data. Notion confirmed that chat transcripts from its Notion AI "Insights" feature were taken, affecting about 1% of its customers. Uber says an intruder used a service provider's stolen credentials to reach Uber data held with that provider, and TechCrunch reports that the provider is Fireworks.

Cursor, the AI coding app, says the attacker obtained an access key Cursor had given Fireworks and used it to copy a storage bucket of old coding-agent sessions, mostly from 2025, kept for training. Only sessions not in Privacy Mode were stored there. A small number still contained passwords and API keys, the secret strings that let one program log in to another. From those, the attacker reached internal tools Cursor uses, then, on 29 October, placed a fake copy of Anthropic's Claude Code extension in Cursor's extension marketplace. Cursor says Anthropic did not publish it and it was not a flaw in Anthropic's product.

The fake extension was available for about 11 hours, and Cursor says at most 5,000 users could have received it. It sent details about the computer to the attacker, added the attacker's SSH key, which works like a spare house key for remote logins, and tried to open a hidden connection back to the attacker. Cursor says that last step fails on most Mac and Windows computers because it needs administrator rights, but it asks everyone affected to clean up anyway. Cursor's last sight of the attacker was on 1 November.

# Cursor's check on a Mac: is the attacker's key there?
$ grep -qs svc-telemetry ~/.ssh/authorized_keys \
    && echo "key found" || echo "no key found"
  • Cursor's recommendation: if you installed Claude Code 2.1.312 or 2.1.313 from Cursor's marketplace on 29 Oct, run its check (above for Mac; Windows version in its notice), and if the key is there, its remediation script
  • Cursor says uninstalling the extension may not be enough, because the payload leaves scripts that keep running
  • Cursor's recommendation: rotate the passwords and keys that computer could reach, from another, trusted computer
  • Cursor says sessions in Privacy Mode were not exposed; it is in Cursor's settings

Source: Cursor security notice, 29 Oct · Cursor incident update, 13 Nov · TechCrunch on Fireworks and Notion, 12 Nov · TechCrunch on Uber, 13 Nov

More this week

HIGHCVSS 8.1CVE-2026-119977WORDPRESS

Your WordPress site can be taken over while it updates itself

WordPress released version 7.1.4 as a security release. Its announcement lists "a weakness in the WordPress upgrade process which can lead to remote code execution during the upgrade window", meaning an attacker can make the server run their own commands. WordPress recommends that you update your sites immediately, from the Dashboard under Updates, then Update Now. Sites set up for automatic background updates start the update on their own.

CISA added the flaw to its Known Exploited Vulnerabilities list, its catalogue of flaws with confirmed attacks, on 3 Nov. Its entry describes a race condition, which is two events whose timing the attacker exploits: during a full-package core upgrade, WordPress uses file locations that are predictable and reachable from the web, so an unauthenticated attacker, one with no account on the site, can run code on the server while the upgrade is under way. CISA set a deadline of 6 Nov for US government agencies. NVD, the US government's vulnerability database, scores it 8.1 out of 10.

WordPress says the fixes are being backported, meaning also released for older versions, to every branch that gets security fixes, currently back to 4.7, and that those releases "will ship as they become ready". The same 7.1.4 release also fixes a number of stored XSS flaws, where an attacker plants script that then runs in other people's browsers.

  • WordPress's recommendation: update to 7.1.4 immediately; if you are on an older branch, update when its backported release ships
  • Check Dashboard, then Updates, to see which version your site is on

Source: WordPress 7.1.4 announcement, 28 Oct · CISA KEV, 3 Nov · NVD · Patched 7.1.4, 28 Oct

HIGHCVSS 8.1CVE-2026-123158SERVER ACCESS

An SSH server on Alpine Linux can be logged into with no password at all

SSH is the standard way to log in to a server from afar, and sshd is the program that listens for those logins. Alpine Linux, a small Linux system common in Docker images and cheap virtual servers, warns that an attacker who can reach your SSH port can log in without knowing any password: it takes one connection, works every time, and needs no retries. The attacker needs the name of an account with no password set, which is normal for accounts that use key login only, and the machine needs at least one other account that does have a password. The attacker then sends a very long password, 257 to 1024 bytes.

Alpine says you are affected if you run its openssh-server package, or openssh-server-pam with UsePAM no, with PasswordAuthentication left at its default of yes, and the machine has an account whose password field is *. PAM is the Linux login framework; openssh-server-pam with UsePAM yes is not affected. Alpine explains the mechanism: musl, Alpine's standard C library, returns * when a password is longer than 256 bytes, and * is also what an account with no password stores, so the two match. OpenSSH's release notes call it a "password authentication bypass" that affects some Linux systems built and run without PAM, and say the root cause lies outside sshd but can be avoided in it. CISA added it on 9 Nov.

Alpine says the fixed packages are in releases 3.21.10, 3.22.8, 3.23.8 and 3.24.4, and that upgrading the package does not restart a running sshd, so it must be restarted too. If you cannot update, Alpine says to set PasswordAuthentication no; "either one closes the hole."

# Alpine's recommended fix, then restart the running daemon
$ apk upgrade -U -a
$ rc-service sshd restart
  • Alpine's recommendation: update openssh and restart sshd; the fixed upstream version is OpenSSH 10.6p2
  • Alpine's check: look in /var/log/messages for sshd lines reading "Accepted password" for an account that has no password
  • Alpine says Docker containers that do not run sshd are not affected

Source: Alpine security advisory, 5 Nov · OpenSSH 10.6p2 release notes, 5 Nov · CISA KEV, 9 Nov · NVD · Patched OpenSSH 10.6p2, 5 Nov