Window: approximately 11 November 09:00 SGT to 12 November 09:00 SGT. New and overnight developments, deduplicated against the 11 November edition, with gaps stated plainly.
Attackers used compromised MSP instances’ own “Run Command” to push a rogue client and toolkit; Huntress tracks 6 MSPs, 286+ endpoints, 47 organisations. The toolkit traps any technician who connects.
26.13.1 / 24.22.3 / 22.23.5 fix 16 CVEs, seven High. Worst is CVE-2026-123864, an HTTPS heap-memory disclosure that can expose TLS private keys. No exploitation reported.
About 130 files from 48 mutual-finance firms, about 850 records, entered by a fake account impersonating a Financial Supervisory Service official. IP-count figures conflict across outlets.
The four 9 November KEV additions (GPUStack, FreeSWITCH, Aspera Faspex, OpenSSH) fall due today with no new development, so they are not carried forward as watchlist rows.
An active ScreenConnect campaign is hitting MSPs — and N-able’s N-central is still burning. Attackers used compromised cloud-hosted ScreenConnect instances’ own “Run Command” feature from 01:48 SGT today to push a rogue client and a PowerShell toolkit onto every reachable host; Huntress is tracking 6 compromised MSPs, 286+ endpoints across 47 organisations, and the toolkit traps any technician who connects to an infected host. ConnectWise points, unvalidated, at third-party extensions. Separately, N-able completed its hosted N-central upgrade at 09:04 SGT yesterday after the 9 November public release of 33 alleged zero-days with PoC code (“Able2Shell”); scanning tied to the published PoCs is now observed, though no customer-server compromise is confirmed. Both tools are the remote-access layer MSPs use to manage small banks — treat both as patch-and-hunt priorities today.
Japan’s SMBC group disclosed a third breach in a week, and Korea’s sector assessor breach grew clearer. SMBC Nikko Securities confirmed unauthorised access to its employee stockholding-association administration system, with personal data of up to 56,487 members leaked or possibly leaked — names, addresses, holdings and transfer-destination account details. In Korea, the Financial Security Institute breach is now scoped at about 130 files from 48 mutual-finance firms (about 850 records), entered by a fake account impersonating a Financial Supervisory Service official; the reported attacker IP count conflicts across outlets (more than 100, 236, about 246 — all said to be domestic Korean), and an FSI official’s suggestion that AI was “likely” used is an estimate, not confirmed. No new KEV additions were made on 11 November.
Node.js shipped its security releases, Apache fixed a critical mod_http2 RCE, and Fortinet published two more critical FortiMail flaws. Node.js 26.13.1 / 24.22.3 / 22.23.5 fix 16 CVEs, seven High — worst is CVE-2026-123864, an HTTPS heap-memory disclosure that can expose TLS private keys and other users’ requests; no exploitation or public PoC reported, and Node.js published no CVSS scores. Apache 2.4.71 fixes CVE-2026-119618, a critical mod_http2 race condition leading to remote code execution (2.4.55–2.4.70). Fortinet’s two new FortiMail criticals (CVE-2026-126263, 9.8 SQL injection; CVE-2026-126155, 9.1 unauthenticated IBE webmail session hijack) were both found with the help of an AI model — the same week Microsoft’s FORGE Lab showed AI-assisted scanning producing 33 kernel CVEs. Unit 42 published the week’s clearest ARTEX picture: 1,323 internet-facing CyberStrikeAI hosts and 609 ARTEX hosts, with a behavioural hallmark table defenders can hunt on; and Arctic Wolf reported AntiFox, an ARTEX fork, being used to steal AWS credentials. A 9 November Datadog report, missed by earlier editions, shows ARTEX hunting financial data inside AWS environments in October.
Group Name | Target Sub-sector / Geography | TTPs (MITRE ATT&CK where available) | Impact
| Group | Target | TTPs | Impact |
|---|---|---|---|
| Unknown actor — ScreenConnect campaign — NEW (confirmed, active, 12 Nov) | Managed service providers and their clients; MSPs serve small banks and financial firms | No MITRE mapping published. Attackers used compromised cloud-hosted ScreenConnect instances’ legitimate “Run Command” feature to install a second, attacker-controlled ScreenConnect client plus a PowerShell toolkit on every reachable host. Toolkit installs scheduled task “TrapWatch” running as SYSTEM every 10 seconds, and a modified client impersonating the legitimate client that delivers the toolkit to any technician who connects — a reverse-pivot trap. | Confirmed (Huntress, Sophos, ConnectWise Trust Center). Campaign began ~17:48 UTC 11 Nov (01:48 SGT 12 Nov). Huntress tracking 6 compromised MSPs, 286+ affected endpoints across 47 organisations, numbers climbing. ConnectWise’s early assessment points to third-party ScreenConnect extensions as the deployment route — five extensions disabled across ~400 partner environments as a precaution — but this is explicitly unvalidated and root cause is not established. Initial access also unconfirmed: Huntress telemetry points to compromised credentials and hijacked MSP support sessions. A batch script referencing rogue client ID 2588ef5c15954b10 was first uploaded to VirusTotal 25 July 2026, suggesting that client ID saw earlier malicious use. No exfiltration claim so far — persistence/access, not yet a data-theft disclosure. No financial institution confirmed among the 47 organisations. Not tied to CVE-2026-84869 (September guest file-transfer issue). |
| Unknown actor — SMBC Nikko Securities — NEW (confirmed, 11 Nov) | Securities firm, Japan; members of employee stockholding associations at listed companies | No MITRE mapping published. Attacker and entry route not disclosed; investigation ongoing. | Confirmed (company disclosure, 11 Nov; reported by NHK 14:34 SGT, Nikkei 12:00 SGT). Unauthorised access to the system administering employee stockholding associations (mochikabu-kai) — used to run share-purchase schemes of listed companies. Anomaly detected 7 Nov; access confirmed 9 Nov; access blocked and service suspended the same day; investigation then confirmed the leak. Data leaked or possibly leaked, varying by association: association names, investment holdings, member identification numbers, names, addresses, dividends and taxes, shareholding balances, transfer-destination account information. Maximum 56,487 members — the number whose data was leaked or may have been, not a confirmed per-field count. Telephone numbers and email addresses were not registered in the system and did not leak. No secondary harm confirmed at disclosure; no trading impact — the system cannot execute share trades. Dedicated helpline 0120-715-250. Separate incident from the SMBC Consumer Finance breach (5 Nov) and the SMBC email-contractor leak — a different SMBC Group company and system. Third SMBC Group disclosure in a week; firms should review whether group-wide or shared-service weaknesses are in play. |
| Unknown actor — Korean Financial Security Institute — Update, previously covered | Financial-sector security assessment body, South Korea; assessment staff at banks, insurers, securities firms | No MITRE mapping published. Attacker created a fake account impersonating a Financial Supervisory Service (FSS) official, exploiting a weakness in the authority-approval process to gain FSS-level access and view/download submitted material. No actual FSS account was taken over and no FSS account data leaked, per FSI. | New in-window (11 Nov): scope clarified — about 130 files from 48 financial companies; about 200 administration forms; about 300 personal records (names, dates of birth in forms such as credit-information consent samples); about 350 system-user records (partly masked names, phone numbers, email addresses). Total personal records about 650; one Korean report totals the items at about 850 (200 forms + 300 + 350). All 48 affected firms are mutual-finance firms (regional agricultural cooperatives / Nonghyup, credit unions / Shinhyup, forestry cooperatives); no large firm among them, per FSI. FSI says network diagrams / vulnerability-analysis results, resident registration numbers and customer credit information were not leaked. Concentrated attacks 9 Nov ~13:00–14:00 KST; FSI detected abnormal access and blocked the system at 14:19 KST on 9 Nov. Response in-window: FSC and FSS began an emergency on-site inspection on the morning of 11 Nov; Seoul Metropolitan Police Agency cyber unit took up the investigation (FSI handed over IP logs). FSI apologised, will notify affected firms and individuals, re-check its whole information-protection system, and compensate if secondary harm occurs. FISCON 2026 (FSI’s annual conference, 12 Nov): VIP event fully cancelled; start delayed from 08:20 to 10:00. Background surfaced 11–12 Nov: a February 2022 FSC special audit had warned FSI about leak risk from the same system (staff could view submitted evidence from home PCs) and asked for stronger security — whether FSI acted adequately is now a live question, not a finding. Figure conflict — flag, do not smooth over: attacker IP count is reported as “more than 100”, 236, all domestic/Korean (Herald Business, citing FSI), and about 246, all domestic (Byline Network, 11 Nov 17:56 KST). The 236 figure is the most specifically attributed to FSI. One FSI official is quoted as saying AI use is “likely” given the short intervals between attempts — this is an FSI estimate, not confirmed AI use. |
| Falcon C2 / XG — NEW (Unit 42, 11 Nov; China-nexus espionage, per secondary summary) | Government webmail portals and web apps in one Middle Eastern country and four Southeast Asian countries; ministries of foreign affairs, defence and interior, law enforcement | No MITRE mapping published. Falcon (aka XG / Xiàng Gē) is a Node.js C2 framework running malicious JavaScript inside victims’ browsers. Operator injected scripts into government webmail portals and web apps (Mar–May 2026); 39 Roundcube webmail instances compromised in the Middle Eastern country’s Ministry of Foreign Affairs portal (script tag injected into the portal header; credentials intercepted on sign-in). Steals passwords, emails, session cookies, communications. Sideloads a fake “PDF Viewer” Chrome/Firefox extension (Manifest V3, version 2026.5.13.1, 40 permissions, <all_urls> host access; Chrome extension ID mbidcmlcbgbphpoacojjbmfpohcimjji) giving full browser control: credential/cookie theft, clipboard hijacking, download interception/replacement, network hooking (fetch/XHR), Gmail/Discord/Zalo exfiltration, Twitter/X DM scraping, using the victim browser as an authenticated proxy for session hijacking. Also delivers a Rust implant, Antino, using Microsoft OneDrive as a C2 channel (via a fake Flash update). C2 panel hides behind a blank page, login revealed only after pressing F9 three times; victim-facing listener serves Tetris/Snake decoys. | Confirmed (Unit 42 research, 11 Nov; campaign Mar–May 2026, published 11 Nov). Unit 42 assesses with high confidence Falcon and PeckBirdy (Trend Micro, Jan 2026) are variants of the same core framework (shared URL structures, AES/RSA key exchange, Baidu-mimicking Hm_lvt_ session markers). Operator not named by Unit 42; related references point to China-nexus activity that has also used Antino (per secondary summary — treat as reported, not Unit 42 attribution). BFSI relevance indirect but material: the technique (compromised webmail + malicious browser extension + session hijacking) directly threatens bank staff credentials and sessions. Hunt markers: Hm_lvt_ local-storage/cookie keys, the extension ID, unexpected browser extensions, Roundcube script-tag injection. Unknown: how the extension was first installed (Unit 42: likely social engineering or a small deployment utility; no sample recovered); the initial-access vector into the webmail portals; victim counts beyond the 39 Roundcube instances. |
| AntiFox — NEW (Arctic Wolf Labs, 10 Nov; reported 11 Nov) | AWS environments; internet-facing web services (IIS); no victim sector named | No MITRE mapping published. AntiFox is an open-source, Chinese-language agentic penetration-testing platform, a fork of ARTEX 0.1.1 (AGPL, created on GitHub in October; ~474–482 stars, ~251–252 forks; now at v2.0), hosted by attackers on Alibaba Cloud. In several intrusions, AntiFox-linked infrastructure was tied to exploitation of internet-facing web services and AWS environments: ASPX webshell via IIS w3wp.exe, reading web.config/database connection strings, copying config/log files to a web-accessible folder; then valid IAM identities (including assumed EC2 roles) used for credential validation and enumeration across IAM, EC2, S3, Lambda, Secrets Manager, KMS, RDS, ECS, EKS, Redshift, Athena, Glue, Systems Manager, API Gateway, CloudWatch, CloudFormation, DynamoDB and Bedrock. One intrusion cycled through several AWS identities with hundreds of API requests in ~30 minutes; most denied, but a successful GetSecretValue against a production secret and S3 copy/delete operations were confirmed. | Confirmed (Arctic Wolf observed intrusions; no named actor). Entry point in some cases was an IIS application (vulnerability unidentified); in others, a valid AWS credential obtained by unknown means. Arctic Wolf IOCs: two Alibaba-hosted source IPs, AntiFox default port TCP/8787, console title, Boto3 1.43.125 user agents (cloud IPs may be reassigned). No CVE, no attribution to a named group. BFSI relevance high: agentic frameworks automating cloud-credential theft directly threaten banks’ AWS estates; the pattern (web shell → config secrets → cloud enumeration → Secrets Manager) is exactly the attack path against financial cloud workloads. Unknown: IIS vulnerability used; how initial AWS credentials were obtained; victim identities/sectors; total scope. |
| ARTEX — Datadog AWS report — Catch-up (published 9 Nov; missed by earlier editions) | AWS environments; financial data — crypto companies, hedge funds and financial institutions | No MITRE mapping published. In-the-wild ARTEX activity inside AWS environments in October 2026, centred on the cloud control-plane view. Entry via compromised long-term IAM access keys and abuse of public Amazon Cognito user pools (anonymous sign-ups, token collection, account enumeration). With a valid key, ARTEX’s most frequent action was CloudWatch FilterLogEvents — every call set with a limit of 1000 — searching for crypto companies, hedge funds and financial institutions; a 20 October session from 103.54.154.40 (zeofast.cn) widened to file and storage links, secrets, internal IPs and database information. A 26–27 October Cognito spike from 154.64.252.77 used the user agent Mozilla/5.0 ARTeX. In early November Datadog tied ARTEX activity to IPs resolving to a hosted console and found hundreds of additional internet-exposed ARTEX consoles, often in Mandarin and hosted in Singapore and Hong Kong; rebranded consoles seen: ScopeWeaver, LUCK, Guanlan SEC. | Confirmed (Datadog Security Labs, 9 Nov — published outside this window; included as a catch-up because earlier editions missed it). Datadog attributes on its own telemetry; no named victims and no confirmed exfiltration are stated. Its “hundreds of consoles” is not blended with Censys’s 1,465 (4 Nov), Check Point’s 1,608 live (5 Nov) or GitGuardian’s 1,428 (7 Nov scan) — different denominators and methods. 154.64.252.77 already appears in the tracker page under the WorkOS entry of 6 November — the same address in a different incident, not a new IOC. New IOCs: 10 IPs and 10 user agents (see Indicators). BFSI relevance high: ARTEX was searching directly for financial institutions and their data. |
| Aoqin — Tyfone — NEW (reported / unconfirmed) | Digital/mobile banking platform provider, US; its customers are credit unions and community banks | No MITRE mapping published. No intrusion detail published. | Unconfirmed — threat-actor claim only. Aoqin, described by multiple trackers as an emerging group, lists Tyfone on its leak site (discovered 11 Nov 09:51 UTC / 17:51 SGT). Claimed data: 35 GB; categories “contracts, banking, clientsData, personal”; status “Not paid”; data-publication date 19 Nov 2026, 09:14 UTC. Tyfone (founded 2004, ~200 employees) provides digital/mobile banking to US credit unions and community banks. Conflict to flag: Undercode News, citing the same Dark Web Intelligence report, says the listing contains no data volume, file count or sample — only a company profile. The 35 GB figure comes from Ransomware.live/QPulse’s reading of the leak entry, not from a sample. Tyfone has not publicly confirmed an incident; no data sample or technical evidence was supplied. No evidence any Tyfone customer bank was compromised. Watch item, not a confirmed breach. |
| INC_RANSOM — Raymond James Financial — NEW (reported / unconfirmed) | Diversified US financial-services firm (wealth management, investment banking, capital markets, asset management, banking) | No MITRE mapping published. No intrusion detail published. | Unconfirmed — threat-actor claim only, explicitly unverified by BreachSense (discovered 11 Nov). Victim listed as raymondjames.com; claimed by INC_RANSOM. No data volume, sample, or company confirmation shown; no corroborating mainstream reporting found. Do not conflate with two separate, earlier Raymond James matters: a Massachusetts AG filing dated 30 Jan 2026, and a July 2026 incident at Werth Wealth Management (a separate firm whose clients hold Raymond James accounts; Raymond James said its own accounts were not accessed). Neither is the 11 Nov INC_RANSOM claim. |
| Blind Eagle (APT-C-36) — Catch-up (disclosed 10 Nov 23:58 SGT; missed by the 11 Nov edition) | Judicial, financial and educational organisations, focused on Colombia and Brazil | No MITRE mapping published. ~3,300 phishing emails late Oct–early Nov, fake court / fiscalía / tutela lures in Spanish/Portuguese, HTML-smuggling / ZipCrypto, AsyncRAT / DCRat-lineage RAT. | Reported (Zenox report via The Hacker News, 10 Nov 15:58 UTC). Zenox could not confirm any successful compromise. Included here because the disclosure fell inside yesterday’s window and yesterday’s edition missed it — not as a new 11–12 Nov development. |
| Qilin — administrator identified — NEW (reported, researcher assessment) | Ransomware-as-a-service operation; financial firms among victims generally | No MITRE mapping published. No new IOCs, CVEs or technical indicators in the piece. | Reported — researchers’ attribution, not law-enforcement confirmation (KrebsOnSecurity, 11 Nov). Researchers (IntelHawk, Intel 471, Flashpoint, SpyCloud, Constella, Ke-la, “Gang Exposed”) link the handle “Haise” — administrator of Qilin, described by NCC Group as the world’s most active ransomware-as-a-service operation with ≥365 victim organisations claimed in the past three months — to a 36-year-old man from St Petersburg, Russia, via linked forum handles (“Rjun”, Telegram “Alexbigboss44”), a RAMP forum application (June 2022) and leaked Gosuslugi records. Qilin has operated since Sept 2022; affiliates keep ≥80% of extortion payments; the leader has claimed on Telegram to have worked with Scattered Spider and RansomHub. Treat the identity claim as an intelligence assessment, not definitive proof (Krebs itself flags possible errors in breach records). Useful context for threat modelling/sanctions, not an operational change. |
| Unknown actor — N-able N-central — Update, previously covered | RMM platform used by MSPs serving small banks and financial firms | No MITRE mapping published. Researcher Sean Bales (GitHub “Oracle-Security”) published the “Able2Shell” repository on 9 Nov with PoC code for 33 alleged N-central flaws, including an unauthenticated chain to RCE/root (XXE in service import → session theft → password reset → command execution as the nable user). | New in-window: N-able confirmed all hosted N-central servers upgraded by 11 Nov 01:04 UTC (09:04 SGT, 11 Nov — just inside the window) to hotfix 2026.4 HF2 (build 2026.4.1.26, released 10 Nov), fixing seven CVEs (see watchlist). N-able now reports “scanning activity associated with the published proof-of-concept code”. watchTowr/Beazley and Previdian report exploitation attempts against honeypots/decoys, not confirmed compromise. Huntress: no evidence of Able2Shell exploitation in partners’ environments as of 10 Nov. A follow-up hotfix is planned; N-central’s built-in remote-control feature stays disabled until a future fix. American Banker (11 Nov 22:19 UTC): this is N-central’s third security emergency since August, and many small banks’ IT providers (MSPs) use N-central to manage and access bank systems. Still unknown: whether any customer server has been compromised (none reported as of 10–11 Nov), mapping of the seven CVEs to the 33 findings, and the follow-up hotfix date. |
| Unknown actor — SMBC Consumer Finance — No new development in-window | Consumer finance, Japan; customers of partner banks, credit unions and online banks | No MITRE mapping published. | No change in-window. Total remains up to 320,118 as announced 5 Nov. The 10 Nov SMS individual-notification start (sender 0005000365) and the “at least 26 banks” count are pre-window. |
| Unknown actor — Mirae Asset Securities — No new development in-window | Securities brokerage, South Korea | No MITRE mapping published. | No change in-window. FSS on-site inspection began 9 Nov (previously covered). Figures unchanged: ~3,800 customer account numbers; 35,255 staff personal data. |
| Unknown actor — Philippine SEC — No new development in-window | Securities regulator, Philippines | No MITRE mapping published. | No change in-window. The NPC’s 10 Nov announcement that 10 government agencies (incl. SEC, BIR, DICT) had filed breach notifications was reported on 11 Nov (Rappler 11 Nov 20:11 SGT), but the announcement itself is 10 Nov and pre-window in substance. NPC disclosed no victim counts, data types, or whether incidents are connected. SEC facts unchanged: detected 6 Nov, notified NPC 9 Nov; names, usernames, emails, mobiles, birth dates, genders, addresses and TINs may have been exposed; no passwords leaked, no data altered, no company records affected (per SEC). |
| Unknown actor — Crédit Mutuel Arkéa — No new development in-window | Cooperative banking group, France | No MITRE mapping published. | No change in-window. |
| Marlanwg — Bank Rakyat — No new development in-window | Cooperative bank, Malaysia | No MITRE mapping published. | No change in-window. |
| Storm-3358 — No new development in-window | Financial sector, Southeast Asia | No MITRE mapping published. | No change in-window beyond the Unit 42 ARTEX post above, which is vendor analysis of the same tooling, not a new campaign, victim or tool development. |
| Deadlock — Fidex, Coopebis, Kadick — No new development in-window | Insurance broker (Mexico); savings and credit cooperative; agency banking (Nigeria) | No MITRE mapping published. | No change in-window. All three remain leak-site claims only. |
| N0n / Krybit — No new development in-window | Wealth management, Canada; payment-card network, US; conglomerate with insurance interests, Australia | No MITRE mapping published. | No change in-window. The 9 November listings remain leak-site claims only, no victim named, no data released. |
| TraderTraitor — Binance — No new development in-window | Crypto exchange, global | No new MITRE list in-window. | No change in-window. No Recovery Update #10 has been published. |
No new in-window item was found for Insight Credit Union, Vanguard Group, Gopax, Mercado Bitcoin, NTT Docomo, AU Small Finance Bank, Pekin Insurance, Higginbotham, Qilin / AXE – EXPERTS, the two unnamed Canadian firms (8 Nov), Scry Analytics, FIN7 / Carbanak, Scattered Spider, RansomHub, Cl0p, or a FI-specific Initial Access Broker. Absence of reporting is not evidence of absence of activity.
CVE ID | CVSS Score | Affected Product | Exploitation Status | Relevance to Finance
No new CISA KEV additions were made on 11 November. The catalogue stands at 1,779 entries (13 November additions: 4 on 9 Nov, 6 on 10 Nov, 3 earlier in the month). The four 9 November KEV additions (GPUStack CVE-2026-102895, FreeSWITCH CVE-2026-116779, IBM Aspera Faspex CVE-2026-123218, OpenSSH CVE-2026-123158) fall due today, 12 November, with no new attribution, IOCs or PoC in-window — per the standing rule a due date alone is not a new development, so they are not carried forward as watchlist rows. The other five 10 November KEV additions (Outlook CVE-2026-124194, Chrome CVE-2026-125350, Cisco BroadWorks CVE-2026-20320, Openwave CVE-2026-111793) likewise have no new development in-window and are not carried forward; only Barracuda is carried, on the new telemetry below. Verification limit: the CISA KEV page fetch returned a stale 7 November crawl (1,769 entries), so the “no new additions” conclusion rests on the absence of any 11 November-dated addition reporting across multiple sources plus the 1,779-entry count as of the 11 November sync — not a live catalogue read.
| CVE | CVSS | Product | Status | Finance relevance |
|---|---|---|---|---|
| CVE-2026-123864 NEW 11 NOV | High — no CVSS published | Node.js 22.x / 24.x / 26.x (HTTPS servers) | Not known exploited — no PoC reported | New in-window (Node.js security releases, 11 Nov). HTTPS heap-memory disclosure: a zero-length TLS write re-enters the HTTP parser, and the server copies other connections’ heap memory — including TLS private keys and other users’ requests — into a request body. Triggering needs a handler that calls res.flushHeaders() before the request body ends and later res.end() with a non-empty chunk; reading the leaked memory needs an ordinary route that echoes or stores a request body. Cleartext node:http not affected. Fixed in 26.13.1 / 24.22.3 / 22.23.5. Five of the 16 CVEs are credited to Chris Rohlf “in collaboration with Claude and Anthropic Research”. Node.js published no CVSS scores and lists no workarounds — upgrade only. Node.js underpins banking web APIs, portals and middleware; a TLS-key leak is a direct credential-theft path. |
| Node.js batch — six further High NEW 11 NOV | High — no CVSS published | Node.js 22.x / 24.x / 26.x | Not known exploited — no PoC reported | New in-window. CVE-2026-123863 (HTTP/2 remote abort via reachable assertion in session teardown; unauthenticated client crashes a default server; 24.x/26.x; variant of CVE-2024-27983); CVE-2026-123865 (HTTP/2 session/file-descriptor leak during shutdown; 22.x/24.x/26.x; incomplete fix for CVE-2026-48937); CVE-2026-123866 (HTTP/2 stream teardown sends freed response memory, including other connections’ buffers, to a peer; 22.x/24.x/26.x); CVE-2026-123872 (TLS 1.2 renegotiation lets a client switch servername and carry client-cert auth to a host with a stricter policy; 22.x/24.x/26.x); CVE-2026-123874 (HTTP/2 use-after-free in respondWithFile()/respondWithFD() streams; 24.x/26.x); CVE-2026-126051 (remote TLS server crash via deferred handshake callbacks; 24.x/26.x). Six Medium and three Low complete the 16-CVE release, plus dependency bumps (llhttp, undici, sqlite, brotli 1.2.1). One aggregator lists 17 CVE IDs for this release while Node.js states 16 — report Node.js’s count. Unauthenticated remote DoS and memory disclosure against internet-facing services. |
| CVE-2026-119618 NEW 11 NOV | Critical — no CVSS yet | Apache HTTP Server 2.4.55–2.4.70; standalone mod_h2 2.0.8–2.0.42 | Not known exploited — no PoC reported | New in-window (Apache 2.4.71, 11 Nov). Race condition in mod_http2 assign_headers() — concurrent requests corrupt shared heap data, leading to remote code execution. Found by Anthropic’s OSS Scanner (reported 26 Oct) and Anthony Weems / Simon Scannell of Google Cloud Vulnerability Research (3 Nov). Fixed in httpd 2.4.71 (or patch mod_http2/mod_h2 with commit 824beab9b942); disabling HTTP/2 is a mitigation. Apache httpd fronts many banking web apps, APIs and customer portals; unauthenticated RCE on a public web server is a direct initial-access path. Also fixed in 2.4.71: CVE-2026-106023 (Important, mod_md NULL pointer dereference, child-process crash, 2.4.30–2.4.70) and CVE-2026-109163 (Low, mod_vhost_alias 1-byte stack buffer overwrite, 2.4.69–2.4.70). NVD lists CVE-2026-119618 as awaiting analysis. |
| CVE-2026-126263 NEW — PSIRT 10 NOV | 9.8 | FortiMail 8.0.0–8.0.1, 7.6.0–7.6.4, 7.4.0–7.4.6 | Not known exploited — no PoC reported | New (Fortinet PSIRT, 10 Nov; CVE records surfaced 11 Nov). SQL injection (CWE-89): an authenticated attacker can execute unauthorised code/commands via crafted requests. Fixed in 8.0.2 / 7.6.7 / 7.4.7; FortiMail Cloud already remediated. Internally discovered by Fortinet’s product-security team “with the use of Frontier AI model: Claude Mythos”. FortiMail is a mail security gateway widely used by financial firms; SQLi-to-code-execution on the mail gateway threatens confidential client/bank correspondence. |
| CVE-2026-126155 NEW — PSIRT 10 NOV | 9.1 | FortiMail 8.0.0–8.0.1, 7.6.0–7.6.6, 7.4.0–7.4.8, 7.2 all versions | Not known exploited — no PoC reported | New (Fortinet PSIRT, 10 Nov; CVE records surfaced 11 Nov). Incorrect authorisation (CWE-863): an unauthenticated remote attacker can obtain an authenticated IBE webmail session as any IBE recipient and read or send their encrypted mail via crafted HTTP requests. Fixed in 8.0.2 / 7.6.7 / 7.4.9; 7.2 must migrate to a fixed release; FortiMail Cloud remediated 5 Oct. Also internally discovered with the Frontier AI model Claude Mythos. Hijack of encrypted-mail (IBE) sessions threatens confidential correspondence. Separate from the 10 Nov FortiOS/FortiManager batch covered yesterday. |
| Able2Shell — seven CVEs NEW — HF2 10 NOV | 9.3 (highest) | N-able N-central | PoC public — exploitation unconfirmed (scanning observed) | New in-window. Researcher Sean Bales (“Oracle-Security” on GitHub) published the “Able2Shell” repository on 9 Nov with PoC code for 33 alleged N-central flaws, including an unauthenticated chain to RCE/root (XXE in service import → session theft → password reset → command execution as the nable user). Hotfix N-central 2026.4 HF2 (build 2026.4.1.26), released 10 Nov, fixes seven CVEs: CVE-2026-125883 (XXE, 9.3), CVE-2026-125878 (OGNL injection), CVE-2026-125879, CVE-2026-125880, CVE-2026-125881 (SSRF), CVE-2026-125882 (RCE via path traversal), CVE-2026-91000. All hosted servers upgraded by 11 Nov 01:04 UTC. N-able reports scanning activity associated with the published PoC code; watchTowr/Beazley and Previdian report exploitation attempts against honeypots/decoys, not confirmed compromise; Huntress saw no evidence of exploitation in partners’ environments as of 10 Nov. The Able2Shell PoC repository (Oracle-Security/CVEs, path “0-Days/N-Central N-Able”, 26 Python PoC scripts) is a genuine researcher disclosure — linkable as the PoC source, with the caveat that N-able has not validated all 33 findings. RMM used by MSPs serving small banks; an unauthenticated RCE with public PoC plus observed scanning is a live patching priority. |
| CVE-2026-121653 CATCH-UP — 10 NOV | 9.8 | Ivanti Endpoint Manager Core, 2024 SU7 and earlier | Not known exploited — no PoC reported | Catch-up: published 10 Nov 15:33 UTC (23:33 SGT) — inside yesterday’s window, but the 11 Nov edition missed it; included here plainly as a catch-up, not as 11–12 Nov news. SQL injection in EPM Core allows a remote unauthenticated attacker to achieve remote code execution. Ivanti released five advisories on 10 Nov fixing 13 vulnerabilities across five products; Ivanti says it is not aware of any customers being exploited, and none of the 13 CVEs is in CISA KEV. Fix: EPM 2024 SU8. Sibling critical: CVE-2026-121683 (9.4, missing authentication in Cloud Services Application 5.0.8 only — add/delete trusted EPM Core certificate entries; fix 5.0.8.1; dual-NIC setups not externally exploitable). Sentry CVE-2026-105425 (7.2, RCE, admin privileges required). Citrix also patched the same day (19 flaws combined across both vendors) — Citrix detail not verified here. Endpoint management servers are high-value targets with broad admin reach into bank endpoints. |
| CVE-2026-116606 / CVE-2026-111560 STATUS — KEV 10 NOV | 9.3 / 8.6 | Barracuda Email Security Gateway (116606); Barracuda ESG, ADC, Message Archiver, WAF, WAF CC, WSG (111560) | In the Wild (KEV) — exploitation ongoing | New in-window development: Previdian observed 17 exploitation attempts against CVE-2026-116606 between 9–11 Nov, from 15 IP addresses in three countries (SecurityWeek, 11 Nov 07:53 UTC / 15:53 SGT). Barracuda had already confirmed exploitation against a small number of organisations. KEV due 13 Nov. Pre-auth authorisation bypass (116606) chained with OS command injection (111560) gives unauthenticated root on the ESG. Fixed in ESG 9.4.0.030 and the other products’ fixed releases listed yesterday. Patch now — active exploitation is ongoing in-window. |
| VSA-2026-062 (no CVE ID yet) | — no CVSS assigned | Xen Orchestra / Xen Orchestra Appliance | Actively exploited | No change in-window. Empty-object login token gives Admin privilege; full XCP-ng host takeover as root. Fixed in Xen Orchestra 6.9.1 / 6.10.0. IOCs: 91.211.251.112:8001 and Tor domain ustar3rqxgnskzgnwkgpofgtvxevm6cx3lxdbwt4mndtveqyaohid.onion:3333. |
| SAP November Patch Day — four CVSS 10.0 | 10.0 | SAP NetWeaver AS ABAP / Web Dispatcher / Gateway | Not known exploited | No change in-window. CVE-2026-76964 (ICM memory corruption, unauthenticated RCE — “ICM2SHELL”), CVE-2026-89126 (Web Dispatcher memory corruption, unauthenticated RCE), CVE-2026-89103 (Gateway broken access control), CVE-2026-120017 (SAML2 missing authentication). Patch internet-facing systems first. |
| Fortinet batch — eight criticals | 9.8–9.0 | FortiOS / FortiManager / FortiAnalyzer / FortiSASE | Not known exploited | No change in-window. Worst CVE-2026-126170 (9.8, JSON RPC API). Fixed in FortiOS 7.2.14/7.4.13/7.6.8/8.0.2 and FortiManager/FortiAnalyzer 7.2.13/7.4.12/7.6.8/8.0.2 — some fixes still “upcoming”; apply the FortiGuard virtual patch, keep OFTP/FGFM ports off the internet. |
| Microsoft November Patch Tuesday | Up to 9.9 | Microsoft enterprise stack (Exchange, SharePoint, SQL Server, AD, LDAP, DNS) | One exploited (Outlook CVE-2026-124194, not carried — see note above) | No change in-window. 1,094 newly released CVEs, 64 Critical. Notable criticals, none reported exploited: SharePoint CVE-2026-120002 (9.9); SQL Server CVE-2026-116945 (9.8); Windows Search CVE-2026-116928 (9.8, zero-click); LDAP CVE-2026-119958 (9.8, zero-click, unauthenticated); Windows DNS CVE-2026-88218 (9.8); iSCSI CVE-2026-88234 (9.8); Exchange CVE-2026-118207 (8.8); AD DS CVE-2026-118146 (8.8); Schannel CVE-2026-119952 (8.1). |
| CVE-2026-88771 | 9.5 / 9.8* | Citrix NetScaler ADC and NetScaler Gateway | In the Wild (KEV) | No change in-window. Public Metasploit module (6.5.9, 6 Nov). Unauthenticated pre-auth command injection as root via attacker-controlled text written to appliance logs, later executed by maintenance script ns_monuploadd_err.pl — execution can lag the request by up to 24 hours. In KEV since 27 Sept. Fixed in 14.1-73.37 and 13.1-64.23. Patching does not remove existing implants. *CVSS v4.0 9.5 (Citrix) vs v3.1 9.8 (NVD). |
| CVE-2026-76443 | 9.8 | Cisco Secure Email Gateway and Secure Email and Web Manager, 15.5 and earlier | In the Wild (KEV, sibling) | No change in-window. Public Metasploit module (6.5.9, 6 Nov). Rapid7 describes the module as an S/MIME/email-parsing SQL injection leading to unauthenticated root RCE — treat the CVE mapping as Rapid7’s, not Cisco’s. The actively exploited zero-day in the same family is sibling CVE-2026-76461 (9.8, in KEV since 14 Sept). |
| CVE-2026-97229 | 10.0 | GitLab CE / EE | In the Wild (KEV) | No change in-window. Public Metasploit module (6.5.9, 6 Nov). CI/CD RegExp integer-overflow RCE as the git user; authenticated, requiring write access to a public project. In KEV since 29 Oct. |
| CVE-2026-119977 | 8.1 / Low* | WordPress core 4.7.0–7.1.3 | In the Wild (attempts) | No change in-window. 240,000+ blocked attempts (peaking at 74,000+ on 30 Oct). Still no victim publicly named and no confirmed compromise. Fix 7.1.4 / backport; block web access to wp-content/upgrade/ before updating. Public PoC: lysophavin18/CVE-2026-119977 (GitHub). A second repo claiming to bypass the 7.1.4 fix holds no code, only a download link — flagged as a likely malware lure, do not download. *Wordfence 8.1 vs WordPress Low. |
| CVE-2026-107441 | 8.8 (Zyxel) / 9.8* | Zyxel GS1900 series switches, ten models, web management interface | In the Wild (zero-day) | No change in-window. June fix added a check that ran after the unsafe copy in /cgi-bin/dispatcher.cgi, so June-patched firmware stayed exploitable. Payloads: Jitterly backdoor and Sixzut rootkit; suspected Chinese-speaking actor Kapibala/Red Heron (attribution via Binarly/Acronis, not independently verified). *Secondary analysis rates it 9.8. Not in KEV as of 7 Nov. Fix: 22 Oct firmware; change default credentials. |
| CVE-2026-109593 / 109594 | 9.1 / 6.8 | SonicWall Global Management System 9.5.2 and earlier (end-of-life) | Not reported exploited in-window | No change in-window. 109593 critical (9.1): unauthenticated information disclosure via internal file reads. 109594 medium (6.8): high-privilege SQL injection. SonicWall will not patch — migrate to Network Security Manager. |
| CVE-2026-72898 | 10.0 | Metabase 58+ (free and paid editions) | In the Wild | No change in-window. CSA Singapore warned 4 Nov that this SQL-injection flaw, fixed 6 Aug and on KEV since 11 Aug, is actively exploited and a PoC is public. Public PoC: 4minx/CVE-2026-72898 (GitHub), referenced in CSA alert AL-2026-158. Safe releases: 58.24, 59.21, 60.17, 61.11, 62.9, 63.5+. |
| CVE-2026-109618 / 109619 (PHP2Shell) | 9.2 | PHP; PAN-OS and other network/security products | In the Wild | No change in-window. CSA 3 Nov: PAN-OS management interfaces exploited, chained with CVE-2026-46300 to root. Keep management interfaces off the internet. |
| CVE-2026-40217 | 8.8 | LiteLLM proxy | In the Wild (LLMjacking) | No change in-window. User-ID rebind to PROXY_ADMIN. Update LiteLLM, lock endpoints off the internet, rotate keys. |
| CVE-2026-98432 | 9.8 | Linux kernel IPv4 TCP, 4.4+ | Research exploit only | No change in-window. Demonstrated exploit needs MPTCP; RHEL fixed kernels require reboot, Ubuntu was still in -proposed on 3 Nov. |
| CVE-2026-58115 | 10.0 | Node-RED / Siemens IoT2050 | In the Wild | No change in-window. Port 1880 without adminAuth remains an active target. Siemens scope revision noted 8 Nov (more SIMATIC IoT2050 models). |
| CVE-2026-111497 | 9.2 | Google Brotli; Cisco and Splunk products (Node2Shell) | In the Wild (KEV) | No change in-window. Scope as of 5 Nov: 19 Cisco products affected, dozens under investigation, about a dozen Splunk products also affected. Same Brotli root cause also affects ClickHouse (CVE-2026-116366 below). KEV federal due date fell 10 November, but per the KEV rule a deadline alone is not a new development. |
| CVE-2026-19868 | 7.5 / 7.1* | SonicWall SonicOS SSLVPN (Gen7 and Gen8 firewalls) | In the Wild (KEV) | No change in-window. Advisory SNWLID-2026-0014 updated to v1.1 on 9 Nov. A user holding valid credentials for an alternate authentication method can bypass SAML authentication controls on SSLVPN, and may also bypass SAML-enforced MFA. KEV 6 Nov, due 20 Nov. Fixed in 7.3.4-7013 / 8.2.3-8015. No workaround. *NVD 7.5 vs SonicWall 7.1. No verified public PoC — possible fake/malicious repos unverified, not linked. |
| CVE-2026-124079 | 9.8 | rConfig Core 8.0.0–8.2.18 / Pro before 8.4.1 | Not known exploited — no PoC confirmed | No change in-window. Deserialisation of untrusted data lets an unauthenticated network attacker execute arbitrary code via the Redis-backed Laravel Horizon queue. Fixed in Core 8.2.19 and Pro 8.4.1. |
| CVE-2026-58868 | Critical | Android 14–17 | Not known exploited | No change in-window (November Android security bulletin). Critical RCE without user interaction. No CVSS figure, exploitation evidence or PoC in sources read; bulletin date not independently verified from the primary bulletin. Flagged as thinly sourced. |
| CVE-2026-123551 | 10.0 | OpenAM 14.0.0–16.1.3 | Not known exploited — no PoC (vendor withheld) | No change in-window. OpenAM broadcasts live session tokens on the notification WebSocket when agent notifications are enabled (default); agent-only check bypassable unauthenticated. Fix 16.1.4. Workarounds published. |
| CVE-2026-123550 | 9.8* | OpenAM before 16.1.4 | Not known exploited — no PoC | No change in-window. SAML v2.0 SP accepts unsigned assertions on ECP/HTTP-Artifact bindings when WantAssertionsSigned is false. *cve.now lists 9.3; 9.8 is the figure used by most trackers. Fixed in 16.1.4. |
| CVE-2026-114432 | 9.8 | Contact Form 7 6.2–6.2.3 | Not known exploited — no PoC reported | No change in-window. Unauthenticated arbitrary file upload (RCE on stock Apache). 10,000,000+ installs. Fix 6.2.4. |
| CVE-2026-107331 | 9.9 | IBM DataStage on Cloud Pak for Data | Not known exploited — no PoC reported | No change in-window. Remote authenticated attacker can obtain sensitive information via absolute-path traversal. Sibling CVE-2026-107330 (7.7) arbitrary file write. Also in the 8 Nov IBM batch: IBM Concert CVE-2026-6715 / CVE-2026-15266 (both 9.8, unauthenticated OS command injection, fixed in 3.1.0). |
| CVE-2026-96652 / 96654 / 96655 / 96656 (Plex2Shell) | — | Plex Media Server on NAS devices | In the Wild (KEV) | No change in-window. Synology advisory SA-26:17 (8 Nov): fixed package 1.43.5.11079. Updating does not remove installed payloads. In KEV since 20 October. |
| CVE-2026-120984 | 9.1 | Red Hat Build of Keycloak, client management with authorisation services enabled | Not known exploited — no PoC | No change in-window. Authenticated attacker with high-privilege client-management access can upload a malicious JavaScript policy, leading to arbitrary code execution. No fix version listed in sources checked. |
| CVE-2026-118267 | 8.1 | WordPress WP Data Access plugin, 5.5.89 and earlier | Not known exploited — no PoC | No change in-window. Incorrect authorisation allows unauthenticated privilege escalation via key/val parameters on app/update. |
| CVE-2026-116366 | 9.5 | ClickHouse Server, via bundled Brotli 1.2.0 | Not known exploited — PoC unverified | No change in-window. Unauthenticated RCE through bundled Brotli 1.2.0 — same root cause as CVE-2026-111497. Fixed by Brotli 1.2.1. Aggregator-listed PoC/lab repo not verified — not linked. |
No new core-banking, SWIFT/payment-gateway or enterprise file-transfer CVE was reported in this window beyond the items above.
See Threat Actor Activity for the full detail. The BFSI point: ScreenConnect is the remote-access tool MSPs use to manage client endpoints; many small banks and financial firms rely on MSPs. A compromised MSP is a direct path into financial-institution endpoints, and the technician trap turns incident response itself into a spread vector. Huntress’s instruction: do not connect to any affected host with ScreenConnect from any instance until the incident-report steps are complete; lock down the instance (reset every user password, revoke all sessions, enforce MFA, remove unknown users, review session groups / extensions / Toolbox); treat every technician workstation that connected to an affected host as compromised until checked; rotate credentials used on or stored on affected hosts — domain admin, service, backup, hypervisor and browser-saved credentials first. Block at firewall/DNS: 185.99.255.28, 155.94.150.39, newnewnew.gotdns.org, soxnewwork.homedns.org, sc.payproofkit.com, ns.mo7sen.dev.
See Threat Actor Activity and the watchlist. Rapid7 added Suricata detection rules and unauthenticated remote checks on 11 Nov. American Banker notes this is the third N-central security emergency since August. Follow-up hotfix still planned; built-in remote control temporarily disabled. Researcher Sean Bales renamed his GitHub account and deleted his disclosure policy on Wednesday (American Banker).
Baker Tilly Advisory Group (US accounting/tax/advisory firm, Baker Tilly International network, US$6.8bn revenue 2025) became aware 6 Sept 2026 of an incident involving a platform operated by a third-party service provider used to serve clients; an unauthorised actor obtained data relating to certain clients. Review of affected data completed 28 Oct; client letters mailed 9 Nov. The notification gives no total victim count, does not name the provider, and leaves data types as a per-recipient placeholder. Texas Attorney General portal lists 10,456 affected Texas residents, with SSNs, full names, addresses and other information. Baker Tilly says no evidence of unauthorised activity on its own network, no reports of identity theft/fraud linked to the exposure, and is offering 24 months of Experian credit monitoring. Law enforcement notified. BleepingComputer found no ransomware-group claim. Classic third-party concentration risk for a financial-services adviser holding client PII/SSNs; the unnamed-provider gap is itself the lesson — firms cannot assess exposure without knowing which vendor platform was hit.
See Threat Actor Activity. If true, a supply-chain risk to US credit unions and community banks via their digital-banking provider; treat as a watch item, not a confirmed breach.
FinCEN’s order designating MEXC Global a primary money-laundering concern (6 Nov) was published in the Federal Register on 10 November (91 FR 72420, doc. 2026-22962) — the ban on US financial institutions transmitting funds to/from MEXC takes effect 10 December 2026, with no end date. Binance moved immediately: from 10 November it rejects withdrawals to MEXC addresses and holds MEXC-origin deposits for compliance review, listing 13 entities (MEXC Global Ltd, MEXC Estonia OÜ, GIDA Technology AG, MEXC Singapore Pte Ltd and affiliates); affected users risk account restrictions. OKX warned users on 7 Nov. MEXC says it operates normally, user assets secure, reviewing the order; reported outflows of >$120m are exchange/analyst figures, not independently verified. Figure conflict — flag: Treasury’s release says “at least $16 billion” in allegedly illicit transactions (May 2021–May 2026); the FinCEN order text as quoted by several outlets says $16.7 billion. Do not present one figure as settled. Sub-components reported: ~$1.5bn linked to Russian sanctions evasion incl. Garantex/Grinex; FinCEN also cites >$1bn daily volume and ~$5bn reserves (Sep 2026 per Treasury; Jun 2026 per the order text — another small date conflict in secondary reporting). The order does not freeze customer assets or shut MEXC down globally. US banks, brokers and money transmitters must screen MEXC-linked transfers from 10 Dec; exchanges are already enforcing early, so payment/treasury teams may see rejected or held MEXC-linked flows now.
Notion says the Fireworks AI breach exposed Notion AI chat transcripts in a small number of workspaces — fewer than 1% — from the dataset used for its Insights feature (now disabled). Timeline: Fireworks told Notion on 2 Nov that a small dataset had been accessed (described then as synthetic test data); Notion disconnected from Fireworks, deleted its data and halted training runs by 3 Nov; Fireworks confirmed on 8 Nov that customer data had been accessed; Notion found the transcripts when analysing the dataset Fireworks provided on 8 Nov and contacted affected customers on 9 Nov. For the vast majority of affected workspaces the transcripts were unattributable (no author/workspace labels, no tool-call results). Notion says Fireworks had contractually committed to zero data retention for Notion data — but data was in fact retained from the Fireworks endpoints Notion used. Notion has disabled Insights, stopped serving open-weight models through Fireworks, and advises affected users to rotate any passwords, API keys or credentials pasted into Notion AI. This is a customer-specific impact of the Fireworks incident, not a Notion breach — Notion says its own systems were not breached. AI-supply-chain / data-retention risk: a vendor’s retained inference data became breach data. Exact workspace/transcript counts beyond “<1%” unknown; whether other Fireworks customers’ data was in the same dataset unknown.
Attacker broke build filesystem isolation 20 Oct 07:28 UTC, evicted ~26 hours later; decrypted environment variables from up to 100,000 workspaces (1.85% upper bound, not confirmed actual); linked-account tokens (GitHub OAuth, BYOK agent keys) for 1,852 users exposed and reset; ~$740,000 in unauthorised AI usage on stolen keys, which Railway now says it will absorb if providers do not refund; no account logins with stolen credentials observed; customer database not accessed. Railway says the attacker used “abliterated models with no safeguards and a harness similar to ARTEX”, and that keys were passed to “transfer stations” for distillation use (per Neural Daily’s reading of the report — treat the ARTEX-similarity claim as Railway’s characterisation, not independently verified). Fits Wiz’s “Black October” pattern (nine AI developer platforms, 6–30 Oct). Demonstrates the LLMjacking monetisation chain (stolen keys → resale → fraudulent inference spend) and the third-party risk of hosting/AI platforms that hold API keys and secrets. Financial firms using Railway/Fireworks-style platforms should rotate keys. Actual number of workspaces hit is an upper bound only; the flaw exploited in Railway’s build infrastructure is still described as an “unknown flaw”.
Wiz/Mandiant disclosure was 9 Nov; AWS’s statement (“AWS services were not compromised”) was added 10 Nov (pre-window). IOCs from that disclosure remain: Qubole AWS account 805246085872; IAM principals AIDA3W7DIFLYOLTK63SFS and AIDAJYRRH5Y3A7AAJM2HW; quiam- role-session names; IPs 57.129.54.120 (OVH), 45.83.220.211, 185.209.199.73, 89.37.63.175 (Mullvad exits); sso_agent.iso SHA-256 65f061281c9a712e9502793dc4c5035cae490b84da05f7d4223cefa65ad396e4.
Thai Airways said 9 Nov that ~60,529 passenger records were accessed via Amadeus (Aug 2023–Sept 2026); a Finnair figure of ~116,000 bookings surfaced only via a secondary roundup. No new Amadeus statement in-window. BFSI relevance indirect (travel PII usable for phishing; no payment data reported taken).
Two-month joint operation (1 Sep–31 Oct) by the Singapore Police Force Anti-Scam Centre with DBS, UOB, OCBC and GXS disrupted over 900 scam attempts and averted over $35 million in potential losses; over 27,000 SMS alerts sent to more than 15,000 bank customers. Robotic Process Automation used for upstream detection of potential victims; scam types included e-commerce, job, friend-impersonation, government-official impersonation and investment scams. Currency: AsiaOne writes “$35 million” without specifying SGD/USD — in Singapore context most plausibly SGD, but flag as unverified currency. Bank–police RPA intervention model; government-official impersonation remains a leading type. Related context: an SPF/MAS warning reported in-window notes at least 1,100 government-official impersonation cases with at least S$120m losses, roughly double the same period last year (680 cases, S$67m) — but the warning’s exact date could not be verified from the snippet, so treat the 1,100/S$120m figures as reported-in-window with date unconfirmed.
Fraudsters impersonating bank customer-service staff under the guise of HKMA’s “Money Safe” (HKMA/retail-bank service letting customers lock deposits against outward transfer) trick the public into transferring funds to “unlock” protected money. HKMA states it has no connection with the scam, never contacts individuals about personal financial matters or requests transfers, and has reported the case to Hong Kong Police. Banks should warn customers that no legitimate “unlock” payment exists.
India’s Supreme Court directs WhatsApp and other intermediaries to list measures to prevent digital-arrest scams, and directs RBI to ensure banks compensate victims where bank negligence is established; next hearing 23 Nov. WhatsApp told the court it had already acted against 9,400 accounts. Court reiterated RBI’s proposed KYC Amendment Directions 2026 must require financial institutions to indemnify victims (compensation not less than the amount lost) where the fraud occurred due to the institution’s failure to exercise due diligence. RBI to submit a list of authorised financial institutions; law-enforcement agencies to report FIRs in digital-arrest cases. CJI noted cybercrimes down 50% but victims had still lost Rs 800 crore so far this year. Directions expected to be notified by 30 Nov, implemented by 31 Dec. Fresh in-window cases (11 Nov, local press): Mumbai — 69-year-old retired Mazagon Dock employee duped of ₹15 lakh in a digital-arrest scam by callers posing as CBI officers; Kozhikode — six arrested in “Operation Cy-Hunt” for renting bank accounts to fraudsters, ₹38.65 lakh in transactions; Indore — five arrested under “Operation Matrix” for selling bank accounts to cyber-fraud gangs; Guwahati — man arrested for opening fake HDFC Bank accounts via a Customer Service Point centre, used to park cyber-fraud proceeds (~₹5 lakh in the latest instance). Regulatory, not an incident — but it shifts fraud-loss liability toward banks.
See Threat Actor Activity. ~3,300 phishing emails, fake court/fiscalía/tutela lures, HTML-smuggling, AsyncRAT/DCRat-lineage RAT; no successful compromise confirmed.
Three men charged (SDNY) with wire fraud, aggravated identity theft and money laundering; allegedly used AI-generated voices and video of CEOs/lawyers (Jul 2024–Feb 2026) to persuade accounting staff to wire money; alleged total >$129m; largest single loss $11.6m at a UK fintech; six itemised losses total ~$32m; arrests in Spain/UK; charges are allegations, defendants presumed innocent. Victims named in the indictment include a Rhode Island bank (~$2.7m) and a Massachusetts mutual-fund company (~$4.6m). DoJ release does not say how voices/images were generated. Fraud-pattern warning for treasury wire fraud via executive voice/video cloning — include only as in-window coverage of an earlier disclosure, not as 11–12 Nov news.
FSI leak gives attackers real assessment-staff contact details and firm names — expect phishing citing the FSI or the evaluation process. SMBC Nikko’s leaked holdings and account details are impersonation material for shareholders. SMBC CF’s SMS from 0005000365 will be spoofed. Philippine SEC notices remain bait; the SEC warns it never asks for passwords or security PINs. Mirae Asset’s leak gives attackers 3,800 customer account numbers plus names, emails and mobiles of 35,255 employees. Binance, Mercado Bitcoin, Gopax and Nubank/Mercado Pago outage messages remain live phishing bait. Verify via official status pages only.
The March 2026 Maine AG disclosure of an August 2025 breach, re-reported — do not present as a new item.
Techniques actually published for this edition. No mapping is invented where a source published none, and older research recirculated in-window is marked as context, not as a new sighting.
| MITRE Technique ID | Technique / behaviour | Seen in this edition | BFSI relevance / detection note | Status |
|---|---|---|---|---|
| No mapping published | Compromised RMM instance’s “Run Command” abused to push a rogue client + PowerShell toolkit; scheduled task “TrapWatch” (SYSTEM, every 10s); modified client traps connecting technicians | ScreenConnect campaign — active 12 Nov | Do not connect to affected hosts from any ScreenConnect instance; lock down the instance, reset passwords, revoke sessions, enforce MFA; treat connected technician workstations as compromised. | Confirmed (Huntress, Sophos, ConnectWise) |
| No mapping published | Unauthenticated HTTP/2 and TLS memory disclosure and DoS: HTTPS heap leak (TLS keys), HTTP/2 assertion crash, session/file-descriptor leak, stream-teardown use-after-free, TLS 1.2 renegotiation servername switch, respondWithFile use-after-free, deferred-handshake TLS crash | Node.js 16-CVE release — 11 Nov | Upgrade to 26.13.1 / 24.22.3 / 22.23.5; no workaround. Hunt for unexplained Node.js process crashes and memory growth on internet-facing services. | Confirmed (vendor); no exploitation reported |
| No mapping published | Race condition in mod_http2 assign_headers() corrupts shared heap data → remote code execution | Apache CVE-2026-119618 — 11 Nov | Upgrade to httpd 2.4.71; disabling HTTP/2 is a mitigation. | Confirmed (vendor); no exploitation reported |
| No mapping published | SQL injection → unauthorised code/commands; unauthenticated IBE webmail session hijack (read/send any recipient’s encrypted mail) | FortiMail CVE-2026-126263 / CVE-2026-126155 — 10–11 Nov | Upgrade FortiMail to 8.0.2 / 7.6.7 / 7.4.7 (126263) and 8.0.2 / 7.6.7 / 7.4.9 (126155); 7.2 must migrate. | Confirmed (vendor); no exploitation reported |
| No mapping published | XXE in service import → session theft → password reset → command execution as the nable user; public PoC; scanning observed | N-able Able2Shell — hotfix 10 Nov, hosted upgrade 11 Nov | Apply HF2 (2026.4.1.26) to on-prem servers; take servers offline until patched; Rapid7 Suricata rules available. | Confirmed (vendor hotfix); exploitation of customer servers unconfirmed |
| No mapping published | Browser script injection into webmail portals; malicious browser extension (40 permissions, <all_urls>) for credential/cookie theft, clipboard hijacking, download interception, network hooking, session hijacking via victim browser as authenticated proxy; Rust implant via OneDrive C2 | Falcon C2 / XG — Unit 42, 11 Nov | Hunt for Hm_lvt_ markers, the extension ID mbidcmlcbgbphpoacojjbmfpohcimjji, unexpected browser extensions, Roundcube script-tag injection. | Confirmed (vendor research) |
| No mapping published | Webshell → config/database secrets → cloud enumeration across 17+ AWS services → Secrets Manager GetSecretValue; valid IAM identities and assumed EC2 roles abused | AntiFox — Arctic Wolf, 10 Nov (reported 11 Nov) | Audit CloudTrail for unusual GetSecretValue / S3 copy-delete from web-server roles; hunt for TCP/8787 and Boto3 1.43.125 user agents. | Confirmed (vendor research) |
| No mapping published | Fake account impersonating the regulator (FSS) via a weakness in the authority-approval process → FSS-level access to assessment material | Korean FSI — confirmed 10 Nov; scope clarified 11 Nov | Check what was submitted through the FSI evaluation system; watch for phishing citing the FSI. | Confirmed (institute); route details unconfirmed; IP-count figures conflict |
| No mapping published | Unauthorised access to stockholding-association administration system; route undisclosed | SMBC Nikko — confirmed 11 Nov | Warn affected members about contact purporting to come from SMBC Nikko or their employer about their holdings. | Confirmed (company); route undisclosed |
| No mapping published | Pre-auth authorisation bypass + OS command injection → unauthenticated root on the email gateway; exploitation attempts continue (17 attempts, 15 IPs, 3 countries, 9–11 Nov) | Barracuda CVE-2026-116606 / CVE-2026-111560 — KEV 10 Nov; telemetry 11 Nov | Patch ESG to 9.4.0.030; take admin interfaces off the internet; watch for unexplained config restores. | Confirmed (vendor + CISA KEV + telemetry) |
| No mapping published | Agentic intrusion hallmarks: think-then-act cadence (bursts of 1–14 requests ~1s apart, then 25–31s pauses); >200 client secrets validated in ~3 minutes; pivots within ~1 minute of a credential download; write-then-delete storage-bucket tests; canary usernames (test@example.com, deadbeefdeadbeefdeadbeef12); parallel targeting of ADCs, VPN appliances, NAS, workforce identity and cloud ports within an hour; 48-second recheck loops for three days; no software vulnerability used — password-reset pages and exposed APIs abused | ARTEX — Unit 42, 11 Nov | Hunt for behaviour, not indicators: canary usernames in IdP logs, first use of a cloud key from a new IP, write-then-delete storage tests, early-phase probing. Remove public attack maps (OpenAPI specs, source maps, tokens in config files); require authentication on every write endpoint; harden password-reset flows. | Confirmed (vendor research) |
| No mapping published | Agentic cloud intrusion: compromised long-term IAM keys and public Cognito user-pool abuse (anonymous sign-ups, token collection, account enumeration); CloudWatch FilterLogEvents with a constant limit of 1000 searching for financial-company names (Fund, Invoice, Billing, LLC); unauthenticated S3 reads opening every session; placeholder-object probes (zzz_nonexistent_abc.txt, Notexist-xyz) before a burst of guesses | ARTEX in AWS — Datadog, 9 Nov (catch-up) | Hunt in CloudTrail and S3 logs: FilterLogEvents limit 1000, Cognito SignUp/InitiateAuth/GetTokensFromRefreshToken followed by ListBuckets/ListSecrets/DescribeParameters, anonymous AWSAccount S3 reads. Rotate long-term IAM keys; lock down public Cognito user pools. | Confirmed (vendor research); no named victims, no confirmed exfiltration stated |
| No mapping published | SQL injection → unauthenticated RCE (EPM Core); missing authentication → add/delete trusted certificate entries (CSA) | Ivanti CVE-2026-121653 / CVE-2026-121683 — catch-up, 10 Nov | Update EPM to 2024 SU8 and CSA to 5.0.8.1 first; prioritise unauthenticated exposure. | Confirmed (vendor); no exploitation reported |
No technique in this edition was published with a MITRE ID in sources read. Recurring-TTP watch note (context only, not a new sighting): MSP and RMM compromise is the thread of this edition — ScreenConnect and N-able both turn the tool that manages bank endpoints into the attack path — and credential theft and valid-account abuse recur across it (the FSI’s fake regulator account, ARTEX’s service-principal and cloud-key abuse, AntiFox’s IAM enumeration, Falcon C2’s browser session hijacking). Hunt for unusual service-principal changes, first-use of cloud keys from new IPs, and RMM sessions outside change windows. The FSI official’s “AI use likely” estimate is not confirmed AI use, and the Bank Rakyat AI speculation remains an unattributed opinion post — neither is counted as a confirmed AI technique here.
AI as a target, AI as a weapon or accelerator, and AI as a risk and control problem for BFSI.
Notion transcripts exposed via Fireworks (NEW, reported 12 Nov 04:54 SGT). Notion says the Fireworks AI breach exposed Notion AI chat transcripts in fewer than 1% of workspaces, from the dataset used for its Insights feature. Fireworks had contractually committed to zero data retention for Notion data; data was in fact retained. Notion advises affected users to rotate any passwords, API keys or credentials pasted into Notion AI. Standing: Railway’s final incident report (primary 10 Nov; secondary reporting 11 Nov) — ~$740,000 in unauthorised AI usage on stolen keys, environment variables from up to 100,000 workspaces (upper bound), linked-account tokens for 1,852 users exposed and reset. Google/Mandiant LLMjacking research (2–3 Nov) — stolen cloud credentials and LLM API keys, fraudulent bills over $100,000 in a single day and up to ~$1m cumulative at some victims, financial services among victims. Google’s 2027 security forecast (summary 11 Nov) names LLMJacking as the monetisation pattern and says attackers are going after proprietary model weights, custom agent skills, prompt libraries and cloud GPU compute — vendor forecast, not findings. Standing controls: key inventory and rotation, endpoint exposure, spend and invocation monitoring with revoke-and-rotate.
Unit 42 ARTEX post and AntiFox (NEW, 11 Nov). Unit 42 (11 Nov): as of October 2026, 1,323 internet-facing hosts running CyberStrikeAI and 609 running ARTEX (21 running both); 14 tools analysed across four categories (recon: ARL, Scope Sentry, Nemo, XingRin, OpenEASD; agent-led testing: CyberStrikeAI, ARTEX, Cairn, PentAGI, AutoHunter; code audit: DeepAudit, AIxVuln; AI-system assessment: AI-Infra-Guard). ARTEX’s author has made the repo closed-source and ceased public development after scrutiny; alternatives are filling the void. Unit 42 IR investigated multiple intrusions where the attacker’s server hosted an ARTEX console; Managed Threat Hunting tracked a coordinated ARTEX campaign against customer cloud environments (retail, consulting, others). Observed intrusions used no software vulnerability — they abused password-reset pages and exposed APIs to reach cloud access, sometimes in under a day. Behavioural hallmarks in the TTP Tracker; hunt back to September 2026. AntiFox (Arctic Wolf, 10 Nov; reported 11 Nov): an ARTEX 0.1.1 fork, Chinese-language agentic pentest platform (~474–482 stars, ~251–252 forks, now v2.0), used to steal AWS credentials — webshell to config secrets to Secrets Manager. Datadog Security Labs (9 Nov; catch-up, missed by earlier editions): in-the-wild ARTEX activity inside AWS environments in October 2026, focused on financial data — entry via compromised long-term IAM keys and abuse of public Cognito user pools; with a valid key, ARTEX’s most frequent action was CloudWatch FilterLogEvents (every call limit 1000) searching for crypto companies, hedge funds and financial institutions; hundreds of additional internet-exposed ARTEX consoles found in early November, often in Mandarin and hosted in Singapore and Hong Kong; rebranded consoles ScopeWeaver, LUCK, Guanlan SEC. No named victims and no confirmed exfiltration stated. Check Point’s October 2026 threat landscape (11 Nov): ransomware hit a record 1,063 reported attacks in October (+35% vs Oct 2025), and new extortion group “n0n” entered the top 3 within a month of starting operations, “relying heavily on AI-assisted tooling” — vendor telemetry, and the AI-tooling claim is Check Point’s characterisation, not independently verified. No new AI-scaled phishing, vishing or deepfake incident was disclosed in-window. The $129m AI voice-clone indictment reported in-window was unsealed 5 Nov — fraud-pattern warning, not new.
OCC examiner framework; UK deepfake survey; AI finding vulnerabilities faster than humans can review them. OCC Bulletin 2026-54 (released 4 Nov; PYMNTS analysis 11 Nov): a framework guiding examiners reviewing banks’ generative and agentic AI use — six pillars / sixteen components; consequence-based classification (autonomous payment agent = Tier 1, internal productivity tool = Tier 4); it creates no new rules and sets no supervisory expectations — examiners assess AI through existing risk categories (fraud, privacy, cybersecurity, third-party). In-window item is the 11 Nov analysis, not a new regulatory action. Digidentity survey (SC Media, 11 Nov): 69% of UK banking customers doubt their bank can detect AI deepfake impersonation; 80% expect banks to use advanced deepfake detection in selfie-based identity verification; 53% say SMS one-time codes are no longer sufficient. Survey data, not an incident — report as such. AI-assisted vulnerability discovery is now a standing fact on both sides: Fortinet’s two new FortiMail criticals were found with the Frontier AI model Claude Mythos, and Microsoft’s FORGE Lab (11 Nov) reports AI-assisted scanning (MDASH; Sonnet 4.6/GPT-5.x) produced 26,502 raw findings → 621 PoC-backed cases → 59 public upstream kernel reports, 33 assigned CVEs (24 High or above), eight confirmed working local root privilege-escalation exploits in lab conditions (including CVE-2026-64563, rhashtable use-after-free, exploitable by unprivileged users via netlink socket diagnostics); fixes merged for 38 of 59 reports; average bug age 8.1 years (oldest, CVE-2026-74544, ≥21 years). Standing: NCSC UK chief executive’s 9 Nov warning of an AI-powered ransomware attack on UK critical national infrastructure being “highly likely” by 2028 is a forecast/assessment, not a new incident. Standing controls: CSA/GovTech/IMDA personal-AI-agent advisory (6 Nov) — do not give agents access to banking, government or healthcare accounts; Sophos malicious AI-agent “skills” research (6 Nov); Haiou “prompt adware” (Check Point, 4 Nov); Elastic’s finding that attackers execute commands through Claude Code and ChatGPT desktop in confirmed intrusions. Also in-window: npm replaced all 122 versions of @apexacc/cli (1.1.8–1.6.2) with a 0.0.1-security placeholder at 06:36 SGT 11 Nov (GHSA-pg98-9cmp-wcf5) — Elastic Security Labs tracks REF8801: npm packages that rerouted AI-agent traffic (prompts, file reads, tool results) through the operator’s API and dropped CloudSyncD (macOS backdoor) and a Telegram stealer; @apexfdn/copilot-mcp (0.1.0–0.11.6) still published and relays server-supplied shell commands to the AI client — treat as attacker infrastructure. Supply-chain risk in AI coding-agent tooling: developers installing these packages expose prompts, code and credentials.