· 4 min read · LNX Inc.

Cursor traces its poisoned extension to a Fireworks AI key

Cursor names a Fireworks AI key as the root of its breach, police share 6.4 million stolen records, PostgreSQL fixes 52 flaws, and two Windows update bugs.

A developer at dusk studying an extension marketplace on a wide monitor, one extension outlined in amber with a warning triangle

CISA added nothing to its exploited list after November 13, so this Sunday, November 15, 2026, brings follow-ups and housekeeping rather than a new fire. Cursor has explained how its marketplace served a backdoored extension. Police have released stolen-login data. PostgreSQL and Microsoft each gave admins work for Monday.

Network

  • Patch Check Point gateways before Monday's deadline. CISA's due date for CVE-2026-123039 is November 16. Install the November Jumbo Hotfix, for example R81.20 Take 174 or later, per sk1000362. Then hunt for PHP2Shell traces as described in the November 14 briefing. R81.10 and R81 get no fix; mitigate them and plan the upgrade.

Microsoft 365 and identity

  • Update: Rotate any credential you ever pasted into a Cursor support ticket. Cursor's November 13 incident update traces the October breach to an access key it had issued to Fireworks AI. Cursor says Fireworks exposed the key. Cursor's list of data taken includes credentials users sent to Cursor support.
  • Rotate the keys on Cursor's list if you got one. The same update says coding-agent traces from sessions outside Privacy Mode held some unredacted credentials. The attacker used them to reach Cursor's SaaS tools. Fewer than 0.01% of customers had API credentials exposed. Team admins were sent lists of specific keys to rotate. Cursor says you were not in the traces if you got no notice.
  • Reread the original extension cleanup. The stolen access also let the attacker place Claude Code extension builds 2.1.312 and 2.1.313 in Cursor's marketplace cache on October 29. The November 3 briefing covered the indicators. Cursor repeats that uninstalling the extension alone may not remove the backdoor.
  • Check client domains against the Operation Endgame data. On November 12, Dutch police announced the seizure of over 6.4 million stolen personal data items from the Gootloader, CastleRAT and StealC operations. Police say the data is shared with Have I Been Pwned, Shadowserver and NoMoreLeaks, among others. Run a domain search on Have I Been Pwned for each client domain you manage. Reset passwords and revoke sessions for any account that appears.

Servers and endpoints

  • Upgrade PostgreSQL to 18.7, 17.12, 16.16, 15.20 or 14.25. The November 12 release fixes 52 vulnerabilities. The worst server flaw, CVE-2026-6460, is rated CVSS 8.8. It lets a database user who can create objects run code as the PostgreSQL operating system account. The vendor lists no workaround. A login is required, so line-of-business servers with shared or application accounts come first.
  • Plan off PostgreSQL 14. The same announcement says 14.25 is the last PostgreSQL 14 release. Older majors are also affected and get no fix.
  • Update client tools as well as servers. The release fixes CVE-2026-116314, which lets a crafted archive make pg_restore run code. It also fixes CVE-2026-116330, a command injection in pg_dump tar restore scripts. Both are rated 8.8. Update the tools on admin workstations and backup hosts, and do not restore dumps from sources you do not trust.
  • Clean WordPress sites that may have hosted Gootloader. The US Justice Department says the operation removed Gootloader from over 100 servers, including compromised WordPress sites. Dutch police say 681 websites were cleaned. On sites you host, reset admin passwords, turn on MFA, remove admin accounts you do not recognize, and update core, themes and plugins.
  • Keep the N-central Legacy API off; HF3 is not out. No N-central 2026.4 HF3 appears on N-able's status page as of this morning. heise reported that N-able postponed it for further checks. The fix is still HF2, the Legacy API disabled, and agents and probes upgraded, as in the November 13 briefing.

Helpdesk

  • Expect failed Word print jobs after November's Windows updates. Microsoft's alert WI1549472 covers Windows 10 or later and Windows Server 2016 or later, as reported by BleepingComputer. Printing can fail when a document holds an image with zero height or width, such as an invisible watermark. Microsoft has published no workaround or fix date. Do not roll back the security update to fix printing.
  • Hold scripted activation and KMS changes. Alert WI1549486 covers slmgr.vbs /skms-domain and slmgr.vbs /ipk, which fail with error 0x80041008 after the November updates, as reported by BleepingComputer. It affects Windows 10 21H2 and 22H2, Windows 11 23H2, and Windows Server 2019, 2022 and 2025. Devices that are already activated stay activated. Microsoft promises a fix in the coming days, so pause imaging steps that run these commands.
  • Check October preview machines that refuse November's update. The same report says the November Windows 11 updates can fail with 0x80070306, 0x800f0989 or 0x800f0993 on systems that installed the October 2026 preview update. Flag those devices in your patch report rather than counting them as compliant.
  • Warn users about fake police emails. Police say emails that claim to be from them and ask you to check your data are fake, as reported by The Hacker News. Check Your Hack replies only after a user enters their own address on the Dutch police site. Tell staff that an unsolicited "your data was found" email with a link is phishing.

Sources

Tell us what's in front of you.

A drawing set, a failing switch, an audit deadline, or a hunch that IT costs too much. We'll tell you who picks it up and what it takes.