Security readout for executives and security teams
Plain-English summary
CVE-2026-36355 affects the Realtek rtl819x Jungle SDK Wi-Fi kernel driver. Debug memory read/write interfaces are reportedly present in production builds without access control. On affected devices, a local unprivileged context could read or modify sensitive kernel memory. No CISA KEV listing or active exploitation evidence is provided.
Executive priority
Treat this as high priority for device inventory and vendor confirmation, especially for routers, gateways, and access points. Business urgency depends on whether your deployed models include this SDK and allow local code execution paths. No confirmed active exploitation is cited.
Technical view
The rtl8192cd driver exposes write_mem ioctl 0x89F5 and read_mem ioctl 0x89F6 debug handlers without access checks. The CVE states _IOCTL_DEBUG_CMD_ is unconditionally defined in 8192cd_cfg.h, compiling these handlers into production builds. Affected scope is all known Realtek rtl819x Jungle SDK versions through v3.4.14B.
Likely exposure
Likely exposure is embedded networking products using the Realtek rtl819x Jungle SDK through v3.4.14B and the rtl8192cd Wi-Fi kernel driver. The CVE record does not provide CPEs or named device models, so product-level exposure requires vendor or firmware verification.
Exploitation context
The CVSS vector is local, low complexity, no privileges, no user interaction, with high confidentiality and integrity impact. Sources do not support remote network exploitation or active exploitation. The main risk is an untrusted local process or already-present foothold abusing debug ioctls.
Researcher notes
Evidence is strongest for the driver-level flaw and SDK version range, but weak for downstream product mapping. The CVE lists CWE-200, CWE-782, and CWE-787. No patch, commit, advisory, or CPE list is included in the provided sources.
Mitigation direction
- Check OEM and Realtek guidance for firmware or SDK updates.
- Inventory devices using Realtek rtl819x Jungle SDK through v3.4.14B.
- For custom firmware, remove or disable production debug ioctl handlers.
- Restrict local shell access and untrusted code execution on affected devices.
- Prioritize exposed edge devices once vendor-affected models are confirmed.
Validation and detection
- Review firmware SBOMs or build metadata for Realtek rtl819x Jungle SDK usage.
- Confirm presence of rtl8192cd Wi-Fi kernel driver in firmware.
- Check source or build configuration for _IOCTL_DEBUG_CMD_ inclusion.
- Ask vendors whether their products include the affected driver and SDK version.
- Perform any ioctl validation only in authorized lab environments.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-200: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-782: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-787: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-36355 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.7 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N2.55.2CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
7.7HighVector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/totekuh/CVE-2026-36355CVE reference, mitre
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Exposure of Sensitive Information to an Unauthorized Actor
Exposure of Sensitive Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Exposed IOCTL with Insufficient Access Control
Exposed IOCTL with Insufficient Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Out-of-bounds Write
Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.