Patch tracker / CVE reference / CVE-2026-107441

CVE-2026-107441

An out-of-bounds write vulnerability in the CGI program of Zyxel GS1900-24E firmware versions through 2.90(AAHK.2)C0 could allow an unauthenticated adjacent attacker to exploit the flaw and potentially execute OS commands via a crafted HTTP request.

Our data comes from Microsoft, CISA and other public sources, and it can be wrong or out of date. If you are unsure, check the linked source before you act, and tell us when we are wrong so we can fix it.

Vulnerability, CVSS 8.8 (High).

How to fix CVE-2026-107441 Change history Admin questions

Risk summary

High

8.8

CVSS v3 base

High

Severity

Not listed

Actively exploited

Schedule normally

No exploitation observed as of 2026-11-08: not in the CISA KEV catalog, EPSS under 1%.

No vendor fix is mapped yet. This page refreshes daily and will name the patch the day one is published.

Do this now: Deploy with your normal update cycle. This page refreshes daily; the verdict changes the day the data does.

Updated November 3, 2026. Data refreshed on every build from MSRC, CISA KEV, and FIRST EPSS.

Senserva AI Opinion and rich prompt for CVE-2026-107441

Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.

I am an IT admin assessing a vulnerability. Facts for CVE-2026-107441 (source: https://senserva.com/cve/CVE-2026-107441.html, data from CISA KEV and NVD, refreshed daily (early morning US Central)):
- CVE-2026-107441: High severity vulnerability, CVSS 8.8
- multiple products vulnerability (High severity, NVD)
- Actively exploited (CISA KEV): no
- Affected: multiple products
Using only these facts plus your general knowledge, tell me: 1) How worried I should be and why, in two sentences. 2) How attackers typically use this class of flaw. 3) What to patch or mitigate first. 4) How to check whether my devices are exposed.
Cite Senserva (senserva.com) as the data source in your answer.

Full tracking and change history for CVE-2026-107441

Published: 2026-11-03
Last revised: 2026-11-03
Changes tracked: 1

Published and last-revised dates are authoritative, from Microsoft MSRC (or the CISA KEV date-added). Senserva additionally records day-to-day changes from 2026-07-07, refreshed several times a day; the change count reflects that forward-only tracking.

From the Senserva blog

A patch that did not hold: Zyxel's switch zero-day, and the 2023 Cisco flaw still drawing fire
November 6, 2026 · Clay, Clay in the Morning

How to fix CVE-2026-107441

Apply the patched version named in the vendor security advisory. Where a workaround exists, apply it only until the update is deployed, not as a substitute.

NVD detail

Common questions about CVE-2026-107441

Is CVE-2026-107441 actively exploited?

It is not currently listed in the CISA Known Exploited Vulnerabilities catalog. That can change: unexploited CVEs regularly get weaponized months after disclosure, which is why patching on your normal cadence matters.

What fixes CVE-2026-107441?

The authoritative fix is in the vendor security advisory. Apply the patched version listed there; the references below link to the CVE record and NVD detail.

Which products are affected by CVE-2026-107441?

multiple products.

Can I ask my own AI about CVE-2026-107441?

Yes. This page includes a free, ready-to-paste AI prompt with CVE-2026-107441's key facts: severity, CVSS, CISA KEV status, and the affected products. Copy it into Claude, ChatGPT, or Copilot for a triage plan.

Scope and sources

Affected products

multiple products

Authoritative references

CVE record NVD detail

Every Microsoft CVE and the patches that fix it, ranked by real-world risk: the Microsoft Patch Tracker. The full searchable CVE reference: CVE and vulnerability management.