Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

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

CVE-2026-75779 Improper Neutralization: top risk today, fix steps

Most urgent: CVE-2026-75779: Improper Neutralization of Special Elements used in an OS Command (“OS Command Injection”) and Cross-Site Requ
High severity (CVSS 8.6). Recommended action: apply the vendor mitigation.

On 23 October 2026, 24 new CVEs were published that we track: 6 critical, 0 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.

Patch these first

CVE-2026-75779: Improper Neutralization of Special Elements used in an OS Command (“OS Command Injection”) and Cross-Site Requ

High severity (CVSS 8.6), priority 46/100 (patch this month). Signals: high severity. Recommended action: apply the vendor mitigation.

References: NVD

CVE-2026-112862: Deserialization of Untrusted Data vulnerability in xnau webdesign Participants Database participants-database

Critical severity (CVSS 9.8), priority 45/100 (patch this month). Signals: critical severity; remotely exploitable, no login, no user action. Recommended action: apply the vendor mitigation.

References: NVD

CVE-2026-16762: An attacker able to supply a crafted XML document to an application using QXmlStreamReader can cause dispropor

High severity (CVSS 8.7), priority 44/100 (patch this month). Signals: high severity; remotely exploitable, no login, no user action. Recommended action: apply the vendor mitigation.

References: NVD

CVE-2025-30052: The rsyncd service of the CGM CLININET is vulnerable to Authentication Bypass via IP spoofing

High severity (CVSS 8.8), priority 42/100 (patch this month). Signals: high severity; remotely exploitable, no login, no user action. Recommended action: apply the vendor mitigation.

References: NVD

CVE-2025-30047: CGM CLININET is vulnerable to Remote Code Execution caused by deserialization of untrusted data

Critical severity (CVSS 9.4), priority 41/100 (patch this month). Signals: critical severity. Recommended action: apply the vendor mitigation.

References: NVD

CVE-2026-112860: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in xnau web

Critical severity (CVSS 9.3), priority 41/100 (patch this month). Signals: critical severity; remotely exploitable, no login, no user action. Recommended action: apply the vendor mitigation.

References: NVD

CVE-2026-75775: Improper Neutralization of Special Elements used in an OS Command in certain ASUS routers allows remote user t

High severity (CVSS 7.7), priority 37/100 (routine). Signals: high severity. Recommended action: apply the vendor mitigation.

References: NVD

CVE-2025-30050: CGM CLININET is vulnerable to Code Injection in the RunCGI.pm component, which dynamically imports the module

Critical severity (CVSS 9.4), priority 36/100 (patch this month). Signals: critical severity. Recommended action: apply the vendor mitigation.

References: NVD

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 23 October 2026?

CVE-2026-75779 (Improper Neutralization of Special Elements used in an OS Command (“OS Command Injection”) and Cross-Site Requ) ranks highest, with a priority score of 46/100. Recommended action: apply the vendor mitigation.

Are any of the new CVEs exploited in the wild?

None of the new CVEs were on the CISA Known Exploited Vulnerabilities list when this was written. Keep watching the list, it changes daily.

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