GoDoxy has a Path Traversal Vulnerability in its File API

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.5 · CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N

EPSS

• CVE-2026-33528: 0.51% estimated exploitation activity in the next 30 days; percentile 43.61 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary 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. Root Cause File: internal/api/v1/file/get.go, lines 68-73: - common.ConfigBasePath = "config" — relative path, not absolute - path.Join("config", "../certs/key.pem") normalizes to "certs/key.pem" — escaping config/ - No call to strings.HasPrefix, filepath.Rel, or any containment check exists - The format:"filename" struct tag is an OpenAPI/Swagger annotation only, not enforced by the validator Proof of Concept Environment - GoDoxy v0.27.4…

Published by the source

24 Mar 2026, 16:35 UTC

Last modified by the source

27 Mar 2026, 21:18 UTC

Source last checked

26 Oct 2026, 15:18 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-4753-cmc8-8j9v

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-33528

Advisory: GoDoxy has a Path Traversal Vulnerability in its File API
IDs: CVE-2026-33528, GHSA-4753-cmc8-8j9v
Record: https://patchnext.com/advisories/cve-2026-33528 (revision 1, source checked 26 Oct 2026, 15:18 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/yusing/godoxy 0.27.5. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/yusing/godoxy: affected < 0.27.5; fixed in 0.27.5

## Suggested inspection (read-only)
- Go github.com/yusing/godoxy: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/yusing/godoxy.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-4753-cmc8-8j9v (GitHub-reviewed advisory GHSA-4753-cmc8-8j9v lists affected ranges: Go github.com/yusing/godoxy >=0 <0.27.5)

Commands are suggestions: review each one before running it.