SMB Cybersecurity Intelligence Briefing — October 23, 2026
Good morning! Welcome to October 23, 2026’s SMB Cybersecurity Intelligence Briefing.
Today we’re covering Collabora Online – Built-in CODE Server OS Command Injection Vulnerability (CVE-2026-110447), new vulnerabilities actively being exploited, and the actions you should take today to reduce ransomware, fraud, and downtime risk. Let’s get to it.
Assumed environment today: Profile A (Microsoft 365 + Windows endpoints).
Today’s decision summary
- Patch now: Apply the vendor’s mitigation for CVE-2026-110447 (Collabora Online – Built-in CODE Server) if you run it.
- Harden immediately: Take management pages and remote-administration tools off the public internet; require MFA on administrator accounts.
- Watch closely: CISA’s ransomware flag and the vendor notice for CVE-2026-110447.
- Verify backups: Confirm one backup copy is offline or immutable and restore one file today.
- Employee risk point today: Anyone contacted by a “vendor” asking for a login or remote access: hang up and call back on the number in your own records.
- One control to test: From a phone on mobile data (not your office network), try to open your firewall and remote-tool admin pages; they should not load.
1. Top story of the day
Collabora Online – Built-in CODE Server OS Command Injection Vulnerability (CVE-2026-110447)
- What happened: On Oct 23, 2026 CISA added CVE-2026-110447 to its Known Exploited Vulnerabilities catalog, confirming active exploitation.
- Why it matters: Collabora Online – Built-in CODE Server when used within the NextCloud platform contains an OS command injection vulnerability that allows for remote code execution when the CODE server isn't running. Data exposure and downtime on that system are the risk. CISA lists ransomware use as Unknown.
- Threat type: Exploited Vulnerability
- Who is targeted: Organizations running Collabora Online – Built-in CODE Server (a file-sharing or collaboration server). Industry and region: Not reported.
- Attack path: Initial access: network access, with no privileges required (from the NVD vector). Impact as CISA describes; further detail Not reported.
Action timeline
- Do in 4 hours: Check whether you run Collabora Online – Built-in CODE Server and note its version. If its management page faces the internet, limit it to a VPN or fixed addresses.
- Do in 24 hours: Apply the vendor’s mitigations or updates, or stop using the product if none are available (CISA required action), per the vendor notice below, then run the compromise check.
- Do in 7 days: List every internet-facing system you run and who updates it.
Assume compromise: patching locks out new attackers; it does not evict one already inside. If this system was internet-reachable at any time since exploitation began (start date not reported), run a compromise assessment, not patching alone. CISA also marks this entry for forensic triage. Look for new administrator or local accounts, unfamiliar sign-ins, unexpected outbound connections, unplanned service restarts and configuration changes you did not make. Keep the logs before rebuilding. IOCs: not reported by authoritative sources.
- Verification: In the product’s admin page, compare the installed version with the fixed version in the vendor notice (not reproduced here), then review the account list and recent sign-ins.
- Fallback if you can’t patch today: remove the management page from the public internet (VPN or address allow-list at your firewall) and watch its logs daily.
- If you have no IT staff: Ask whoever manages it: “Do we run Collabora Online – Built-in CODE Server, what version, and when was it updated?” If nobody knows, have them unplug it from the internet.
- Impact score: 4 of 5: exploited and reachable over the network, but it needs specific deployment conditions to be present, and it is rated high for confidentiality, integrity and availability.
- If you use an MSP: “Send me today the installed version of Collabora Online – Built-in CODE Server on every system you manage for us and its last update date, or confirm in writing we do not run it.”
Benchmark only: CISA’s federal due date is Oct 26, 2026; it does not bind your business.
Sources: CISA Known Exploited Vulnerabilities catalog, entry added Oct 23, 2026; NVD record for CVE-2026-110447, published Oct 14, 2026; Vendor or agency notice on help.nextcloud.com (publication date not reported); Vendor or agency notice on github.com (publication date not reported).
2. Active threat & vulnerability updates
Arista VeloCloud Orchestrator: CVE-2026-114625
- Status: Exploited per CISA, added Oct 23, 2026. CISA lists ransomware use as Unknown.
- Affected systems: Arista VeloCloud Orchestrator; versions Not reported by CISA.
- Impact: Arista VeloCloud Orchestrator on-prem contains a SQL injection vulnerability that may allow a remote attacker to access privileged internal functionality and impact the VCO host.
- CVSS: CVE-2026-114625 v4.0 base 9.4 (Critical).
- Business risk: High (24h). Federal due date Oct 26, 2026 (benchmark only).
- Mitigation: vendor mitigations or updates; stop using the product if none exist (CISA required action).
- How to check exposure: find it in your asset list and read the installed version.
Sources: CISA Known Exploited Vulnerabilities catalog, entry added Oct 23, 2026; NVD record for CVE-2026-114625, published Oct 22, 2026.
EG Secure Solutions SiteGuard Server Edition: CVE-2026-106931
- Status: Exploited per CISA, added Oct 20, 2026. CISA lists ransomware use as Unknown.
- Affected systems: EG Secure Solutions SiteGuard Server Edition; versions Not reported by CISA.
- Impact: EG Secure Solutions SiteGuard Server Edition contains an OS command injection vulnerability which may allow an attacker to execute arbitrary OS commands with root or SYSTEM privileges on the system running the affected product.
- CVSS: CVE-2026-106931 v4.0 base 8.5 (High).
- Business risk: Medium (7d). Federal due date Oct 23, 2026 (benchmark only).
- Mitigation: vendor mitigations or updates; stop using the product if none exist (CISA required action).
- How to check exposure: find it in your asset list and read the installed version.
Sources: CISA Known Exploited Vulnerabilities catalog, entry added Oct 20, 2026; NVD record for CVE-2026-106931, published Oct 14, 2026.
Plex Media Server: CVE-2026-96652, CVE-2026-96654, CVE-2026-96655, CVE-2026-96656
- Status: Exploited per CISA, added Oct 20, 2026. CISA lists ransomware use as Unknown.
- Affected systems: Plex Media Server; versions Not reported by CISA.
- Impact: Plex Media Server contains an external control of file name or path vulnerability which can allow an admin user to write arbitrary files that may be executed on load.
- CVSS: CVE-2026-96652 v4.0 base 5.3 (Medium); CVE-2026-96654 v4.0 base 6.9 (Medium); CVE-2026-96655 v4.0 base 5.3 (Medium); CVE-2026-96656 v4.0 base 8.6 (High).
- Business risk: Medium (7d). Federal due dates Oct 23, 2026 and Nov 3, 2026 (benchmark only).
- Mitigation: vendor mitigations or updates; stop using the product if none exist (CISA required action).
- How to check exposure: find it in your asset list and read the installed version.
Sources: CISA Known Exploited Vulnerabilities catalog, entry added Oct 20, 2026; NVD record for CVE-2026-96652, published Sep 23, 2026.
CVSS scores are as published in each NVD record; where NVD has not scored a CVE itself, the score shown was supplied by the CVE’s assigning authority.
1 further addition(s) in the window are listed in the CISA catalog.
3. Security protocols & hardening
Exposure triage for an exploited internet-facing product
- Risk reduced: Intrusion through a flaw attackers are already using.
- Minimal steps:
- Find every instance of the affected product, including old ones nobody owns.
- Take its management interface off the public internet before you update it.
- Apply the vendor’s fix, then run the compromise assessment above.
- Rotate any credentials or keys the product stored.
- Verification: The installed version matches the vendor notice, the management page is unreachable from outside, and the account and configuration review found nothing unexpected.
- Common failure mode: Teams update the product and stop, leaving an intruder who got in before the update, and leave the old management page open.
- Cost: Low. Time to implement: 2 to 4 hours.
4. Tools & technology
Built-in controls first
- Your firewall or router’s published-services list. Minimum configuration: Open the port-forwarding or published-services page and remove entries nobody can name an owner for. Verification: From a phone on mobile data, not your office network, the removed addresses no longer answer.
- The affected product’s own audit log (or Event Viewer on a Windows host). Minimum configuration: Filter for account creation, failed sign-ins and service restarts since you installed it. Verification: You can explain every entry as expected, or you have escalated it.
5. Operational metrics snapshot
CISA’s Known Exploited Vulnerabilities catalog (release of Oct 23, 2026, 3:30 p.m. ET) lists 1,756 entries. In the 7 days to Oct 23, 2026, 8 were added, and 0 of those are marked as used in ransomware campaigns.
Sources: CISA Known Exploited Vulnerabilities catalog, release of Oct 23, 2026, 3:30 p.m. ET.
Closing
Tomorrow’s watch list:
- Any change to CISA’s ransomware flag or the vendor notice for CVE-2026-110447
- Breach notices from your software or service providers
- CISA additions for managed-service tooling
Question of the day: Which supplier could lock us out of our systems or move our money, and when did we last check their access?
Daily security win (10 minutes or less): Pick one vendor and confirm the name of the person at your company who owns that relationship. Risk reduced: Orphaned vendor access. How to verify: The register row shows an owner and today’s review date.
This weekday’s theme: Friday is vendor day, before the weekend, when a supplier problem is hardest to get anyone to answer. Asking for dated answers now means you are not waiting on a reply on Saturday.
Go deeper
This briefing provides general information for operational risk reduction and is not legal, insurance, or incident-response advice. Verify all actions against your own environment and current vendor advisories before applying them. Vulnerability status and patch guidance change rapidly; confirm against the linked sources before acting.