CVE-2026-23699
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 · uneditedAP180 series with firmware versions prior to AP_RGOS 11.9(4)B1P8 contains an OS command injection vulnerability. If this vulnerability is exploited, arbitrary commands may be executed on the devices.
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 · high confidenceThe AP180 series network devices contain an OS command injection vulnerability in firmware versions prior to AP_RGOS 11.9(4)B1P8. This allows authenticated attackers to inject and execute arbitrary operating system commands on the affected devices through the vulnerable firmware component.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Network
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm device is AP180 seriesCheck the device model through CLI command 'show version' or via the web UI system information pageAffected if Device model does not start with AP180
-
Check installed firmware versionRun 'show version' in CLI or view system status in web UI to retrieve the firmware version string (format: AP_RGOS X.X(X)BX)Affected if Unable to retrieve firmware version string
-
Compare version against affected rangeParse the firmware version. Versions prior to AP_RGOS 11.9(4)B1P8 are affected (including 11.9(4)B1, 11.9(3), 11.9(2), 11.9(1), earlier releases)Affected if Installed version is earlier than AP_RGOS 11.9(4)B1P8 (e.g., 11.9(4)B1, 11.9(3), etc.)
-
Verify remote management accessibilityCheck if web-based or CLI management interfaces are exposed to network (review interface configurations, management VLAN settings, or access control lists)Affected if Management interface is reachable from untrusted networks (exploitation requires authenticated access)
Device is affected if it is an AP180 series model running firmware version earlier than AP_RGOS 11.9(4)B1P8 with accessible management interfaces
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade AP180 series devices to firmware version AP_RGOS 11.9(4)B1P8 or later to remediate the command injection vulnerability.
AP_RGOS 11.9(4)B1P8 or later
- 1. Identify the current firmware version of the Ruijie AP180 series device by accessing the web management interface or using the CLI command 'show version'
- 2. Navigate to the official Ruijie support website (www.ruijie.co.jp or global Ruijie networks support) and locate the firmware download section for AP180 series access points
- 3. Download the firmware version AP_RGOS 11.9(4)B1P8 or any later stable release
- 4. Access the device management interface, navigate to the firmware upgrade section, and upload the downloaded firmware file
- 5. Wait for the upgrade process to complete and the device to reboot automatically
- 6. Verify the upgrade was successful by checking the firmware version again and confirming it shows 11.9(4)B1P8 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-23699 — 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-2026-23699 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