# CVE-2023-33865: Path traversal in n/a

> Local attackers can escalate privileges by exploiting a symlink vulnerability in the RenderDoc temporary directory handling.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Jun 2023
- **Updated:** 3 Nov 2025
- **Also known as:** DEBIAN-CVE-2023-33865, GHSA-h6fr-rh94-prmv, UBUNTU-CVE-2023-33865

## What is CVE-2023-33865?

CVE-2023-33865 is a high-severity path traversal vulnerability in n/a, published on 7 Jun 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

RenderDoc before 1.27 allows local privilege escalation via a symlink attack. It relies on the /tmp/RenderDoc directory regardless of ownership.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

## Which versions are affected by CVE-2023-33865?

It affects 1 product.


Products: Renderdoc Renderdoc.

## How do I fix CVE-2023-33865?

Upgrade to a fixed version.

## Is CVE-2023-33865 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-33863](https://insights.sbomify.com/CVE-2023-33863/): Integer overflow in n/a (critical 9.8)
- [CVE-2023-33864](https://insights.sbomify.com/CVE-2023-33864/): Integer overflow in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-33865 and fix it if it is affected.

What it is: CVE-2023-33865 is a high-severity path traversal vulnerability in n/a, published on 7 Jun 2023. 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-2023-33865 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-2023-33865/ (Markdown: https://insights.sbomify.com/CVE-2023-33865/index.md)
```

## Sources

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

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