dbcve.org
Vpn100 FirmwareOperating system · Zyxel

CVE-2022-26532

HIGH · 7.8 CVSS v3.1 Published 2022-05-24
Fix available
A fix is available. Upgrade to after 5.21 or later.
See remediation →
80/100
Remediation priority · High
Public exploit Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A argument injection vulnerability in the 'packet-trace' CLI command of Zyxel USG/ZyWALL series firmware versions 4.09 through 4.71, USG FLEX series firmware versions 4.50 through 5.21, ATP series firmware versions 4.32 through 5.21, VPN series firmware versions 4.30 through 5.21, NSG series firmware versions 1.00 through 1.33 Patch 4, NXC2500 firmware version 6.10(AAIG.3) and earlier versions, NAP203 firmware version 6.25(ABFA.7) and earlier versions, NWA50AX firmware version 6.25(ABYW.5) and earlier versions, WAC500 firmware version 6.30(ABVS.2) and earlier versions, and WAX510D firmware version 6.30(ABTF.2) and earlier versions, that could allow a local authenticated attacker to execute arbitrary OS commands by including crafted arguments to the CLI command.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Vpn100 FirmwareOperating system
Affected:>= 4.30, <= 5.21
Vpn1000 FirmwareOperating system
Affected:>= 4.30, <= 5.21
Vpn300 FirmwareOperating system
Affected:>= 4.30, <= 5.21
Vpn50 FirmwareOperating system
Affected:>= 4.30, <= 5.21
Atp100 FirmwareOperating system
Affected:>= 4.32, <= 5.21
Atp100w FirmwareOperating system
Affected:>= 4.32, <= 5.21
Atp200 FirmwareOperating system
Affected:>= 4.32, <= 5.21
Atp500 FirmwareOperating system
Affected:>= 4.32, <= 5.21

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 5.21
Recommended fix Moderate confidence

Firmware version newer than 5.21 (e.g., 5.21 Patch 1, 5.30, or latest available stable release for your specific model)

  1. 1. Identify the specific device model from the affected product list (Vpn50, Vpn100, Vpn300, Vpn1000, Atp100, Atp100w, Atp200, Atp500)
  2. 2. Access the Zyxel support website at https://www.zyxel.com/support/support.shtml or https://www.zyxel.com/us/en/support/download_os.html
  3. 3. Locate the firmware download section for your specific device model
  4. 4. Download the latest available firmware version for your device. For ATP and VPN series, look for firmware versions newer than 5.21 (e.g., 5.21 Patch 1 or later, or version 5.30/6.0 if available)
  5. 5. Review the firmware release notes to confirm the update addresses CVE-2022-26532 or includes security fixes for the packet-trace command vulnerability
  6. 6. Back up the current device configuration
  7. 7. Upload and install the new firmware via the web GUI or CLI following Zyxel's standard firmware upgrade procedure
  8. 8. After reboot, verify the device is functioning correctly and test that the packet-trace command works properly
Caveat Review release notes for your specific model; some firmware upgrades may require configuration adjustments or have compatibility considerations with certain features or legacy settings

Generated from the published advisory — verify against the referenced sources before acting.

We can identify the exact fixed release, upgrade, and verify it in staging — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-26532 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-26532 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data