Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

Blog · 2-hour update · 2026-10-24

CVE-2026-110447 Collabora Online – Built-in CODE: exploited in the wild, how to patch

Most urgent: CVE-2026-110447: Collabora Online – Built-in CODE Server OS Command Injection Vulnerability
Critical severity (CVSS 9.2), exploited in the wild, remotely exploitable, no login needed. Recommended action: apply the vendor mitigation.

On 24 October 2026, 0 new CVEs were published that we track: 0 critical, 2 already exploited in the wild (CISA KEV) and 0 with a fix or vendor patch available. Each one is ranked by severity, exploitation signals and how easy it is to reach, so you can patch the right ones first.

What happened in this 2-hour window: the most serious item is CVE-2026-110447 in Collabora Online – Built-in CODE Server (critical, CVSS 9.2, priority 82/100). Recommended action: apply the vendor mitigation. 2 new CVEs from the list below are already being exploited (CVE-2026-110447, CVE-2026-114625), so those go first. 1 of the 2 top items can be attacked remotely without a login. 0 of 0 new CVEs already have a fix or vendor patch.

Patch these first

CVE-2026-110447: Collabora Online – Built-in CODE Server OS Command Injection Vulnerability

Critical severity (CVSS 9.2), priority 82/100 (patch now). Signals: critical severity; exploited in the wild (cisa kev); cisa ssvc: automatable with total technical impact. Recommended action: apply the vendor mitigation for Collabora Collabora Online – Built-in CODE Server.

References: NVD

CVE-2026-114625: Arista VeloCloud Orchestrator SQL Injection Vulnerability

Critical severity (CVSS 9.9), priority 71/100 (patch now). Signals: critical severity; exploited in the wild (cisa kev). Recommended action: upgrade to 5.2.3.18, 6.1.3.10, 6.4.2.12 for arista velocloud orchestrator.

References: NVD · Mitigation, Vendor Advisory

How to act on this list

  1. Start with anything marked exploited or patch now.
  2. Check what you run: see how to check a version and patch it on Linux, Windows, pip and npm.
  3. Prefer the vendor or distro fix. If none exists, read when to downgrade and when to mitigate.
  4. Verify afterwards. Distros often fix a flaw without changing the upstream version, here is how to confirm.

FAQ

What is the most serious vulnerability published on 24 October 2026?

CVE-2026-110447 (Collabora Online – Built-in CODE Server OS Command Injection Vulnerability) ranks highest, with a priority score of 82/100. Recommended action: apply the vendor mitigation.

Are any of the new CVEs exploited in the wild?

Yes, 2 of the new CVEs appear on the CISA Known Exploited Vulnerabilities list. Patch those first.

Should I downgrade if there is no fix yet?

Only when an older release is confirmed unaffected and the package is not a core system component. Downgrades can break dependent software, so test first and hold the package until a fix ships.

Sources

← All posts