# CVE-2026-33528: GoDoxy has a Path Traversal Vulnerability in its File API

> An authenticated attacker can exploit a path traversal flaw in GoDoxy's file API to read or write arbitrary files outside the intended directory.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Mar 2026
- **Updated:** 27 Mar 2026
- **Also known as:** GHSA-4753-cmc8-8j9v, GO-2026-4817

## What is CVE-2026-33528?

CVE-2026-33528 is a medium-severity path traversal vulnerability in yusing godoxy, published on 26 Mar 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

GoDoxy is a reverse proxy and container orchestrator for self-hosters. Prior to version 0.27.5, the file content API endpoint at `/api/v1/file/content` is vulnerable to path traversal. The `filename` query parameter is passed directly to `path.Join(common.ConfigBasePath, filename)` where `ConfigBasePath = "config"` (a relative path). No sanitization or validation is applied beyond checking that the field is non-empty (`binding:"required"`). An authenticated attacker can use `../` sequences to read or write files outside the intended `config/` directory, including TLS private keys, OAuth refresh tokens, and any file accessible to the container's UID. Version 0.27.5 fixes the issue.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

3 open source packages ship an affected version, including github.com/yusing/godoxy. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/yusing/godoxy` | Go | All versions | 0.27.5 |
| `github.com/yusing/godoxy` | Go | All versions | 0.27.5 |
| `github.com/yusing/godoxy` | Go | All versions | 0.27.5 |

Products: Godoxy Godoxy.

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

Upgrade github.com/yusing/godoxy to 0.27.5 or later.

## Is CVE-2026-33528 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-33528 is a medium-severity path traversal vulnerability in yusing godoxy, published on 26 Mar 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33528 exists.

Affected packages and fixed versions:
- github.com/yusing/godoxy (Go): affected all versions; fixed in 0.27.5
- github.com/yusing/godoxy (Go): affected all versions; fixed in 0.27.5
- github.com/yusing/godoxy (Go): affected all versions; fixed in 0.27.5

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-33528/ (Markdown: https://insights.sbomify.com/CVE-2026-33528/index.md)
```

## Sources

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

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