dbcve.org
Memory Buffer Bounds ErrorWeakness · CWE-119

CVE-2026-11413

HIGH · 8.8 CVSS v3.1 Published 2026-06-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 security vulnerability has been detected in JingDong JD Cloud Box AX6600 4.5.3.r4546. The impacted element is the function set_macfilter of the file /sbin/jdcweb_rpc. The manipulation leads to stack-based buffer overflow. It is possible to initiate the attack remotely. The exploit has been disclosed publicly and may 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

Stack-based buffer overflow in the set_macfilter function of /sbin/jdcweb_rpc binary in JD Cloud Box AX6600 firmware 4.5.3.r4546 allows remote attackers to potentially execute arbitrary code or cause denial of service via crafted input.

MitigationApply network access controls to limit exposure of the affected device; implement firewall rules to restrict access to the jdcweb_rpc service; monitor for vendor firmware updates.

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
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
    Access the device admin interface or check the physical device label to confirm the model is JD Cloud Box AX6600.
    Affected if Device model is JD Cloud Box AX6600
  2. Check the firmware version
    In the device admin interface, navigate to System Settings or Status page to view the firmware version. Alternatively, run 'cat /etc/version' or 'ubootenv get bootcmd' via console if SSH/telnet is available.
    Affected if Firmware version matches 4.5.3.r4546 exactly
  3. Verify the vulnerable binary exists
    Check if the file /sbin/jdcweb_rpc exists on the device by using 'ls -la /sbin/jdcweb_rpc' through SSH, telnet, or serial console access.
    Affected if Binary /sbin/jdcweb_rpc is present on the device
  4. Confirm MAC filter feature is exposed
    Determine if the MAC filter management feature is accessible via the web UI, API, or RPC service. The set_macfilter function must be callable for the vulnerability to be triggered.
    Affected if MAC filter configuration feature is enabled or accessible on the device

The device is affected if it is a JD Cloud Box AX6600 running firmware version 4.5.3.r4546 with the /sbin/jdcweb_rpc binary present and the MAC filter feature enabled or accessible.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply network access controls to limit exposure of the affected device; implement firewall rules to restrict access to the jdcweb_rpc service; monitor for vendor firmware updates.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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