How severe is GHSA-q6gg-9f92-r9wg?

No CVSS score has been assigned to GHSA-q6gg-9f92-r9wg yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-q6gg-9f92-r9wg?

GHSA-q6gg-9f92-r9wg affects the following packages: github.com/traefik/traefik/v2 (Go), github.com/traefik/traefik/v3 (Go), github.com/traefik/traefik/v3 (Go). Ecosystems affected: Go.

How do I fix GHSA-q6gg-9f92-r9wg?

Update github.com/traefik/traefik/v2 to 2.11.28 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q6gg-9f92-r9wg is resolved across your whole dependency graph.

How do I detect GHSA-q6gg-9f92-r9wg in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/traefik/traefik/v2. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-q6gg-9f92-r9wg if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-q6gg-9f92-r9wg?

O3 pinpoints whether GHSA-q6gg-9f92-r9wg is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-q6gg-9f92-r9wg actively exploited in the wild?

No public exploit code has been indexed for GHSA-q6gg-9f92-r9wg yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is GHSA-q6gg-9f92-r9wg?

GHSA-q6gg-9f92-r9wg is classified as Path Traversal (CWE-22), CWE-30 (CWE-30). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-q6gg-9f92-r9wg published, and has it been updated?

GHSA-q6gg-9f92-r9wg was published on August 1, 2025 and was last updated on February 4, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

GHSA-q6gg-9f92-r9wg

GHSA-q6gg-9f92-r9wg is a Path Traversal vulnerability in github.com/traefik/traefik/v2. O3 Security confirms whether GHSA-q6gg-9f92-r9wg is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Traefik Client Plugin's Path Traversal Vulnerability Allows Arbitrary File Overwrite and Remote Code Execution

Also known asCVE-2025-54386GO-2025-3835

Published

Aug 1, 2025

Updated

Feb 4, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Blast Radius

3 pkgs affected

🐹github.com/traefik/traefik/v2🐹github.com/traefik/traefik/v3🐹github.com/traefik/traefik/v3

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Summary

A path traversal vulnerability was discovered in WASM Traefik’s plugin installation mechanism. By supplying a maliciously crafted ZIP archive containing file paths with ../ sequences, an attacker can overwrite arbitrary files on the system outside of the intended plugin directory. This can lead to remote code execution (RCE), privilege escalation, persistence, or denial of service. ✅ After investigation, it is confirmed that no plugins on the Catalog were affected. There is no known impact.

Details

The vulnerability resides in the WASM plugin extraction logic, specifically in the unzipFile function (/plugins/client.go). The application constructs file paths during ZIP extraction using filepath.Join(destDir, f.Name) without validating or sanitizing f.Name. If the ZIP archive contains entries with ../, the resulting path can escape the intended directory, allowing writes to arbitrary locations on the host filesystem.

Attack Requirements

There are several requirements needed to make this attack possible:

The Traefik server should be deployed with plugins enabled with a WASM plugin (yaegi plugins are not impacted).
The attacker should have write access to a remote plugin asset loaded by the Traefik server
The attacker should craft a malicious version of this plugin

Warning

As clearly stated in the documentation, plugins are experimental in Traefik, and unsafe plugins could damage your infrastructure:

Experimental Features Plugins can change the behavior of Traefik in unforeseen ways. Exercise caution when adding new plugins to production Traefik instances.

Impact

This vulnerability did not affect any plugin from the catalog. There is no known impact. Additionally, the catalog will also prevent any compromised plugin to be available across all Traefik versions. This vulnerability can allow an attacker to perform arbitrary file write outside the intended plugin extraction directory by crafting a malicious ZIP archive that includes ../ (directory traversal) in file paths.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/traefik/traefik/v2`	all versions	2.11.28
🐹Go	`github.com/traefik/traefik/v3`	all versions	3.4.5
🐹Go	`github.com/traefik/traefik/v3`	≥ 3.5.0-rc1&&< 3.5.0	3.5.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/traefik/traefik/v2. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/traefik/traefik/v2 to 2.11.28 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q6gg-9f92-r9wg is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-q6gg-9f92-r9wg is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-q6gg-9f92-r9wg. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary A path traversal vulnerability was discovered in WASM Traefik’s plugin installation mechanism. By supplying a maliciously crafted ZIP archive containing file paths with `../` sequences, an attacker can overwrite arbitrary files on the system outside of the intended plugin directory. This can lead to remote code execution (RCE), privilege escalation, persistence, or denial of service. **✅ After investigation, it is confirmed that no plugins on the [Catalog](https://plugins.traefik.io/plugins) were affected. There is no known impact.** ### Details The vulnerability resides in the W

O3 Security · Impact-Aware SCA

Is GHSA-q6gg-9f92-r9wg in your dependencies?

O3 detects GHSA-q6gg-9f92-r9wg across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works