Call Rebecca, our AI receptionist, 24/7: (518) 532-8037. Mention your business name when you call.

Daily Hack Report

Daily Hack Report — 10 November 2026

CISA added six actively exploited vulnerabilities to its Known Exploited Vulnerabilities catalog today, including issues in Microsoft Outlook, Chromium-based browsers, and Barracuda email and network appliances. Over the past two days, CISA also listed an OpenSSH login bypass that researchers say is already being used against Linux systems, N-able took its hosted N-central platform offline after a large public disclosure, and the maker of Xen Orchestra warned of an authentication bypass it says is being exploited.

Published 2026-11-10T16:15:00-05:00 · Times on this page that include an offset are shown as published. Dates without a time are the calendar dates given by the source. The site operator is in America/New_York (ET).

This briefing only includes facts stated by the public sources linked in each item. It is not a complete list of threats, not a penetration test, and not a guarantee of security. Severity labels below repeat what those sources said; we do not invent scores or victim counts.

CISA: actively exploited spoofing bug in Microsoft Outlook

CISA: added to the Known Exploited Vulnerabilities catalog (evidence of active exploitation), due date 24 November 2026 for federal civilian agencies under BOD …

What happened

On 10 November 2026, CISA added CVE-2026-124194 to its Known Exploited Vulnerabilities catalog, based on evidence of active exploitation. CISA’s catalog describes a “Microsoft Office Outlook Missing User Interaction for Potentially Unsafe Action Vulnerability” that “allows an unauthorized attacker to perform spoofing over a network.” Microsoft’s update guide lists the same CVE among the Outlook issues covered in the 10 November 2026 Office security updates. Microsoft’s published CVSS 3.1 score for the issue, as recorded in public CVE records, is 6.5 (Medium), with user interaction required.

Who’s affected

Organizations and people who use Microsoft Outlook as part of Microsoft 365 Apps or Office LTSC, according to the product list in public CVE records and Microsoft’s 10 November 2026 Office security-update notes.

Severity (as sources state it)

CISA: added to the Known Exploited Vulnerabilities catalog (evidence of active exploitation), due date 24 November 2026 for federal civilian agencies under BOD 26-04. CISA lists known ransomware campaign use as Unknown, and forensic triage as not required. Microsoft CVSS 3.1: 6.5 (Medium), as published in CVE records.

What to do

  1. Install the 10 November 2026 Office security updates from Microsoft. Microsoft’s release notes list Current Channel Version 2610 (Build 20527.20196) and other channel builds, plus Office LTSC 2024 Build 17932.21140 and Office LTSC 2021 Build 14334.21048, among the updates that day.
  2. Use Microsoft Update, the Microsoft 365 Apps admin center, or your usual patch process so every workstation that runs Outlook actually receives the update.
  3. Treat unexpected Office files and Outlook prompts with care until devices are patched. CISA encourages every organization, not only federal agencies, to prioritize KEV catalog issues.

Sources

CISA: exploited Chromium bug can run code in the browser sandbox

CISA: Known Exploited Vulnerability, due date 24 November 2026 for federal civilian agencies. Known ransomware campaign use: Unknown. Forensic triage: No. CISA’…

What happened

CISA also added CVE-2026-125350 to the KEV catalog on 10 November 2026, based on evidence of active exploitation. The catalog says Google Chromium contains a use-after-free vulnerability in the XML component “that could allow a remote attacker to execute arbitrary code inside the sandbox via a specially crafted webpage,” and that this “could affect multiple web browsers that utilize Chromium, including, but not limited to, Google Chrome, Microsoft Edge, and Opera.”

Who’s affected

Users and organizations running Chromium-based browsers, including Google Chrome, Microsoft Edge, and Opera, as stated by CISA. We do not have an independent count of how many systems are affected.

Severity (as sources state it)

CISA: Known Exploited Vulnerability, due date 24 November 2026 for federal civilian agencies. Known ransomware campaign use: Unknown. Forensic triage: No. CISA’s KEV entry does not publish a CVSS score; we do not invent one.

What to do

  1. Update Google Chrome, Microsoft Edge, and Opera (and any other Chromium-based browser you use) to the latest vendor release. CISA points to Google’s Chrome stable-channel desktop update notes for this issue.
  2. Confirm the update actually applied: in Chrome or Edge, open the About page and allow it to finish checking for updates, then restart the browser.
  3. Until every work browser is updated, be cautious with unexpected links and attachments. A crafted webpage is the attack path CISA describes.

Sources

CISA: Barracuda email and network appliances, two bugs that can be chained

CISA: both are Known Exploited Vulnerabilities. Due date 13 November 2026. Forensic triage: Yes, for both. Known ransomware campaign use: Unknown. CISA’s KEV en…

What happened

CISA added two Barracuda vulnerabilities to the KEV catalog on 10 November 2026, both with evidence of active exploitation, and both with a federal due date of 13 November 2026. CVE-2026-116606 is an authentication bypass on Barracuda Email Security Gateway (ESG) that, CISA says, “could allow an unauthenticated remote attacker to invoke a configuration-import function and restore a crafted, compatible backup archive, resulting in unauthorized modification of the appliance’s global configuration.” CVE-2026-111560 is an OS command injection affecting ESG and several other Barracuda products; CISA says it “could allow an authenticated administrator to inject OS commands that execute with root privileges when the crafted timezone value is subsequently processed.” CISA states that the two vulnerabilities can be chained with each other.

Who’s affected

Barracuda Email Security Gateway (ESG) for the authentication bypass. For the command injection, CISA lists ESG, Load Balancer, Application Delivery Controller (ADC), Message Archiver (BMA), WAF Control Center (WCC), Web Application Firewall (WAF), and Web Security Gateway (WSG).

Severity (as sources state it)

CISA: both are Known Exploited Vulnerabilities. Due date 13 November 2026. Forensic triage: Yes, for both. Known ransomware campaign use: Unknown. CISA’s KEV entries do not include a CVSS score here; we do not invent one.

What to do

  1. If you run any of the Barracuda products named above, follow Barracuda’s security advisory immediately (CISA links the pre-authentication authorization-bypass and command-injection write-up on Barracuda Trust).
  2. Because CISA flags forensic triage for these two issues, check the appliance for unexpected configuration changes, imported backups, new admin accounts, or unusual outbound traffic after you patch. Do not assume a patch alone undoes a prior compromise.
  3. If a managed provider runs the appliance for you, ask them in writing whether it was patched and whether they looked for signs of misuse.

Sources

OpenSSH “SSHole” login bypass is being exploited, CISA and researchers say

CISA: Known Exploited Vulnerability, due date 12 November 2026, forensic triage: Yes, known ransomware campaign use: Unknown. The Hacker News: CVSS 8.1. Bleepin…

What happened

On 9 November 2026, CISA added CVE-2026-123158 to the KEV catalog. CISA describes an “unexpected status code or return value vulnerability” in OpenBSD OpenSSH on Linux “that could allow for authentication bypass.” The Hacker News, reporting the same CISA addition, calls the issue SSHole, gives a CVSS score of 8.1, and says a fix was issued in November 2026. BleepingComputer reports that attackers are actively exploiting SSHole to execute commands, steal credentials, and establish persistent access; it says exploitation attempts began on 5 November, when a proof-of-concept became available, and that GreyNoise recorded the first successful exploitation it observed on 7 November 2026 at 00:46 UTC. In the attacks GreyNoise described, BleepingComputer says the actor ran system and container reconnaissance, queried cloud metadata services, tried to read password hashes and root SSH keys, and tried to change SSH authorized_keys files.

Who’s affected

CISA: OpenSSH on Linux. Reporting cited by The Hacker News and BleepingComputer focuses on musl-based Linux systems, including Alpine Linux. CISA’s notes also point to an Alpine Linux post and the OpenSSH release notes. This is not described as affecting every Linux distribution equally.

Severity (as sources state it)

CISA: Known Exploited Vulnerability, due date 12 November 2026, forensic triage: Yes, known ransomware campaign use: Unknown. The Hacker News: CVSS 8.1. BleepingComputer and GreyNoise, as quoted by BleepingComputer, report successful exploitation in the wild.

What to do

  1. If you run OpenSSH on Linux, especially Alpine Linux, other musl-based systems, or containers built from those images, apply the vendor or distribution update. Sources point to a fix in OpenSSH 10.6p2 and to Alpine’s 5 November 2026 advisory.
  2. Because CISA marks forensic triage as required for federal agencies on this CVE, look at SSH logs, newly added authorized_keys entries, and unexpected use of cloud metadata endpoints after you patch.
  3. Do not expose SSH more widely than you must. Disable password authentication if you do not need it, and prefer key-based logins with MFA on the jump host where you can.

Sources

N-able takes hosted N-central offline after a large public disclosure

N-able described the issues as critical vulnerabilities. The public disclosure is reported as covering more than 30 issues (The Hacker News and Rapid7 say 33). …

What happened

N-able told BleepingComputer it was “actively responding to non-responsible communication of critical vulnerabilities in N-central late Sunday night, November 8, found by an independent researcher.” As a precaution, it said it took its Hosted N-central environment offline on 9 November 2026 and told on-premises customers to temporarily take their servers offline until further notice. The researcher, Sean Bales, published a GitHub project called Able2Shell with proof-of-concept exploits. BleepingComputer reports one described chain uses an unauthenticated XXE issue in N-central’s service-import function to steal a trusted local session, reset an account password, and run commands as the nable user, and that the same exploit can create an enabled Default Administrator account. N-able said at the time of that statement that it had not observed active exploitation. Rapid7, writing as of 10 November, said N-able later reported scanning activity associated with the published proof-of-concept code and still had no evidence that any customer environment had been successfully exploited, and that a hotfix was being developed and validated.

Who’s affected

Customers of N-able N-central, both hosted and on-premises, according to N-able’s statements as reported by BleepingComputer, The Hacker News, and Rapid7. The researcher reported testing N-central Appliance 2026.4.0.31. Rapid7 notes that N-able’s notice did not yet specify a full affected-version range. This mainly concerns managed service providers and the organizations whose devices they manage with N-central, not every small website.

Severity (as sources state it)

N-able described the issues as critical vulnerabilities. The public disclosure is reported as covering more than 30 issues (The Hacker News and Rapid7 say 33). No CVE identifiers are included in the vendor notice, according to Rapid7. N-able has said it has not observed successful exploitation of customer environments; Rapid7 reports that N-able did observe scanning activity tied to the published proof-of-concept code as of 10 November.

What to do

  1. If you run N-central on your own server, follow N-able: take it offline and keep it offline until N-able says it is safe to restore and a hotfix is applied.
  2. If you use hosted N-central, expect the outage N-able announced and watch N-able’s status and incident updates for restoration and the hotfix.
  3. If an IT provider manages your office or website through N-central, ask them whether their console was taken offline, whether they applied N-able’s hotfix, and whether they reviewed admin accounts and remote-access activity from 8 November onward.

Sources

Xen Orchestra maker warns of an authentication bypass it says is being exploited

The vendor, as reported by The Hacker News, calls it a critical authentication bypass and says it is being actively exploited. No CVSS score or CVE ID is given …

What happened

On 10 November 2026, The Hacker News reported that French company Vates VMS warned of a critical security vulnerability in Xen Orchestra that it said is being actively exploited in the wild. The issue is tracked as VSA-2026-062 and, the article says, does not yet have a CVE identifier. According to Vates, as quoted there, a crafted REST cookie can be parsed in a way that lets an attacker authenticate as the owner of an unexpired token and obtain reusable login token IDs, which can lead to Admin privileges, arbitrary code execution on managed pools, and a full XCP-ng node takeover as root. Vates said it was seeing exploitation from IP address 91.211.251.112:8001, which The Hacker News says has been flagged as a RedLine Stealer command-and-control server on VirusTotal, and from a Tor domain published in the article.

Who’s affected

Deployments of Xen Orchestra / xo-server used to manage XCP-ng or Xen pools, according to the Vates advisory as reported by The Hacker News. This is relevant if you (or your host) manage virtual machines with that stack; it is not a general WordPress or shared-hosting issue.

Severity (as sources state it)

The vendor, as reported by The Hacker News, calls it a critical authentication bypass and says it is being actively exploited. No CVSS score or CVE ID is given in that report. We do not invent either.

What to do

  1. If you use Xen Orchestra, update to the fixed versions named by Vates: Xen Orchestra 6.9.1 or 6.10.0 (stable and latest channels), and xo-server 5.211.2 or 5.213.1, as reported by The Hacker News.
  2. If you cannot patch immediately, the same report lists Vates’ mitigations: do not expose Xen Orchestra instances on the internet; block the IP address and domain associated with the malicious activity; block the empty token in a web application firewall or reverse proxy; and rotate all passwords and secrets in Vates VMS if you see indicators of compromise.
  3. After patching, review admin sessions and tokens and rotate credentials if anything looks wrong.

Sources

Need a review of a site you own?

This briefing is public information, not a private assessment of your systems. If you want a consent-only written review of a site, API, or code you are authorized to have tested, start with the signed authorization request. Reviews are AI-assisted and human-approved. They are not a penetration test, a certification, or a guarantee of security.

All reports · RSS