CVE-2022-30526
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 · uneditedA privilege escalation vulnerability was identified in the CLI command of Zyxel USG FLEX 100(W) firmware versions 4.50 through 5.30, USG FLEX 200 firmware versions 4.50 through 5.30, USG FLEX 500 firmware versions 4.50 through 5.30, USG FLEX 700 firmware versions 4.50 through 5.30, USG FLEX 50(W) firmware versions 4.16 through 5.30, USG20(W)-VPN firmware versions 4.16 through 5.30, ATP series firmware versions 4.32 through 5.30, VPN series firmware versions 4.30 through 5.30, USG/ZyWALL series firmware versions 4.09 through 4.72, which could allow a local attacker to execute some OS commands with root privileges in some directories on a vulnerable device.
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 analysisPrivileges are granted, or fail to be dropped, incorrectly, so an action runs with more power than it should. An attacker who reaches that path inherits the excess privilege. The fix is least-privilege throughout, with explicit, checked transitions whenever privilege changes.
General guidance for the improper privilege management class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →
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>= 4.50, <= 5.30>= 4.50, <= 5.30>= 4.50, <= 5.30>= 4.50, <= 5.30>= 4.16, <= 5.30>= 4.16, <= 5.30>= 4.32, <= 5.30>= 4.32, <= 5.30CVSS 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 · scopedLatest firmware version newer than 5.30 (check Zyxel support for exact fixed release)
- 1. Identify the exact model number and current firmware version of the Zyxel device from the affected product list (USG Flex 100W, 200, 500, 700, 50W, USG20W-VPN, ATP800, or ATP700).
- 2. Visit the official Zyxel support website at www.zyxel.com and navigate to the firmware download section for your specific device model.
- 3. Download the latest available firmware version. Based on the affected version range (up to 5.30), look for firmware versions newer than 5.30 that include the security fix for CVE-2022-30526.
- 4. Review the firmware release notes to confirm the version includes the privilege escalation vulnerability fix.
- 5. Back up the current device configuration before proceeding with the upgrade.
- 6. Upload and apply the new firmware through the device's web GUI or CLI interface, following Zyxel's standard firmware upgrade procedures.
- 7. After upgrade completion, verify the device is operational and confirm the new firmware version is installed.
- 8. Test that the CLI command functionality works as expected post-upgrade.
Generated from the published advisory — verify against the referenced sources before acting.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-30526 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-30526 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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