dbcve.org
Ax6600 FirmwareOperating system · Jdcloud

CVE-2026-2563

HIGH · 8.8 CVSS v3.1 Published 2026-02-16
Fix available
A fix is available. Upgrade to after 4.5.1.r4533 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 vulnerability was identified in JingDong JD Cloud Box AX6600 up to 4.5.1.r4533. Affected is the function set_stcreenen_deabled_status/get_status of the file /f/service/controlDevice of the component jdcapp_rpc. The manipulation leads to Remote Privilege Escalation. It is possible to initiate the attack remotely. The exploit is publicly available and might be used. The vendor was contacted early about this disclosure but did not respond in any way.

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 confidence

A remote privilege escalation vulnerability exists in the JingDong JD Cloud Box AX6600 router (versions up to 4.5.1.r4533) in the jdcapp_rpc component. The set_stcreenen_deabled_status and get_status functions in /f/service/controlDevice allow an unauthenticated remote attacker to escalate privileges. The exploit is publicly available.

MitigationSince the vendor did not respond to early disclosure, apply network segmentation to isolate the device, restrict management interface access to trusted IPs only, and monitor for exploit usage until an official patch is available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Ax6600 FirmwareOperating system
Affected:<= 4.5.1.r4533

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model
    Log into the router admin interface or check the device label to confirm the model is JD Cloud Box AX6600
    Affected if Device model is not JD Cloud Box AX6600 (not affected)
  2. Check the installed firmware version
    Access the router admin panel, typically at the gateway IP (e.g., 192.168.0.1 or 192.168.1.1), navigate to System Settings or Firmware Upgrade section, and note the firmware version displayed
    Affected if Firmware version is 4.5.1.r4533 or any version lower than 4.5.1.r4533 (affected)
  3. Verify the jdcapp_rpc component is present
    Check router services or processes via SSH/telnet access if available, or examine firmware filesystem if you have firmware binary access, for the jdcapp_rpc binary or service
    Affected if The jdcapp_rpc component exists on the device (vulnerable code path is present)
  4. Confirm /f/service/controlDevice endpoint is accessible
    From a network-connected host, attempt to access http://<router-ip>/f/service/controlDevice or check router firewall rules to see if this management endpoint is exposed to LAN or WAN
    Affected if The /f/service/controlDevice endpoint is reachable from the network (exploitable)
  5. Assess network exposure of remote management
    Check router firewall settings, WAN access permissions, or port forwards to determine if the router management interface (ports 80/443 or the jdcapp_rpc service) is exposed to the WAN/internet
    Affected if Remote management or the vulnerable service is exposed to WAN or untrusted networks (directly exploitable remotely)

You are affected if you have a JD Cloud Box AX6600 router running firmware version 4.5.1.r4533 or lower, and the /f/service/controlDevice endpoint with jdcapp_rpc component is accessible from your network.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

From vendor data
Upgrade available Upgrade to a release after 4.5.1.r4533
Interim mitigation

Since the vendor did not respond to early disclosure, apply network segmentation to isolate the device, restrict management interface access to trusted IPs only, and monitor for exploit usage until an official patch is available.

Fix this in Ax6600 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-2563 — 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-2026-2563 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