# CVE-2026-92533: Path Traversal in BugTracker.NET

> An authenticated attacker can exploit a path traversal flaw in BugTracker.NET to read arbitrary system files outside the intended directory.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Oct 2026
- **Updated:** 7 Oct 2026
- **Also known as:** GHSA-4gg8-j6f5-xp7v

## What is CVE-2026-92533?

CVE-2026-92533 is a high-severity path traversal vulnerability in BugTracker.NET, published on 7 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Path traversal vulnerability in the BugTracker.NET file download component. The parameter used to specify the file name does not properly validate user-supplied paths. An authenticated remote attacker could enter a manipulated path to access files located outside the intended directory. Successful exploitation could allow the attacker to read system files accessible to the account used by the application.

Weakness: CWE-24 (Path Traversal: '../filedir')

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


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

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

## Is CVE-2026-92533 being exploited?

There is no known exploitation of CVE-2026-92533 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92533 is a high-severity path traversal vulnerability in BugTracker.NET, published on 7 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-92533 in the wild and no public exploit code.

Affected product: BugTracker.NET. 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-92533/ (Markdown: https://insights.sbomify.com/CVE-2026-92533/index.md)
```

## Sources

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

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