# CVE-2026-36355: Missing authorization in n/a

> Attackers can read or modify kernel memory via unauthenticated debug ioctls in the Realtek rtl8192cd Wi-Fi driver.

- **Severity:** High 7.7 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 May 2026
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-j39q-3p58-f4c8

## What is CVE-2026-36355?

CVE-2026-36355 is a high-severity missing authorization vulnerability in n/a, published on 5 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The rtl8192cd Wi-Fi kernel driver in the Realtek rtl819x Jungle SDK (all known versions through v3.4.14B) does not perform any access control checks on the write_mem (ioctl 0x89F5) and read_mem (ioctl 0x89F6) debug handlers, which are compiled into production builds via the unconditionally defined _IOCTL_DEBUG_CMD_ macro in 8192cd_cfg.h

Weakness: CWE-787 (Out-of-bounds Write), CWE-782 (Exposed IOCTL with Insufficient Access Control), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-36355?


## How do I fix CVE-2026-36355?

No fix has been published for CVE-2026-36355 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-36355 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-36355 exists.

Public exploit code:

- CVE-2026-36355: Realtek rtl819x Jungle SDK - Unauthenticated Kernel Memory Read/Write via Debug ioctls (github_poc): https://github.com/totekuh/CVE-2026-36355
- Realtek rtl819x  - Local Privilege (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-36355 and fix it if it is affected.

What it is: CVE-2026-36355 is a high-severity missing authorization vulnerability in n/a, published on 5 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-36355 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-36355/ (Markdown: https://insights.sbomify.com/CVE-2026-36355/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-36355
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-36355
- OSV: https://osv.dev/vulnerability/CVE-2026-36355

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-36355/
Summaries are generated and may contain mistakes; the official description above is the record.