cve.bz

CVE-2026-7256 zyxel wre6505 firmware: OS Command Injection

8.8 highEPSS 1.0%Unsupported when assigned

High (8.8) in zyxel wre6505 firmware. No vendor fix: the product was unsupported when the CVE was assigned. EPSS 1.0% estimated probability of exploitation activity in the next 30 days.

On this page
A command injection vulnerability in the CGI program of Zyxel WRE6505 v2 firmware version V1.00(ABDV.3)C0 could allow an adjacent attacker on the LAN to execute operating system (OS) commands on a vulnerable device by sending a crafted HTTP request.

Severity

CVSS 3.1

8.8 high
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
1.0% (unchanged from 1.0% a week ago; 2.7% 30 days ago) estimated probability of exploitation activity in the next 30 days; 64th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-05-12. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-78 Improper Neutralization of Special Elements used in an OS Command (OS Command Injection)
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-7256 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-7256?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-7256?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-7256 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-7256

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-7256](https://cve.bz/cve/badge/CVE-2026-7256.svg)](https://cve.bz/cve/CVE-2026-7256)

HTML:

<a href="https://cve.bz/cve/CVE-2026-7256"><img src="https://cve.bz/cve/badge/CVE-2026-7256.svg" alt="CVE-2026-7256"></a>

Affected

Versions

From the NVD's CPE matches.

ProductAffected
zyxel:wre6505_firmwarev1.00(abdv.3)c0

Attack patterns (CAPEC)

  • CAPEC-6 Argument Injection Likelihood: High · Severity: High
  • CAPEC-15 Command Delimiters Likelihood: High · Severity: High
  • CAPEC-43 Exploiting Multiple Input Interpretation Layers Likelihood: Medium · Severity: High
  • CAPEC-88 OS Command Injection Likelihood: High · Severity: High
  • CAPEC-108 Command Line Execution through SQL Injection Likelihood: Low · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON