What is CVE-2026-55828?

CVE-2026-55828 is a medium-severity path traversal vulnerability in go.qbee.io/transport (go), affecting versions < 1.26.25. It is fixed in 1.26.25. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.

Which versions of go.qbee.io/transport are affected by CVE-2026-55828?

go.qbee.io/transport (go) versions < 1.26.25 is affected.

Is there a fix for CVE-2026-55828?

Yes. CVE-2026-55828 is fixed in 1.26.25. Upgrade to this version or later.

Is CVE-2026-55828 exploitable, and should I be worried?

Whether CVE-2026-55828 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2026-55828 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2026-55828?

Upgrade go.qbee.io/transport to 1.26.25 or later.

CVE-2026-55828 in go.qbee.io/transport

Q: Which versions of go.qbee.io/transport are affected by CVE-2026-55828?

go.qbee.io/transport (go) versions < 1.26.25 is affected.

Q: Is there a fix for CVE-2026-55828?

Yes. CVE-2026-55828 is fixed in 1.26.25. Upgrade to this version or later.

Q: Is CVE-2026-55828 exploitable, and should I be worried?

Whether CVE-2026-55828 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2026-55828 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2026-55828?

Upgrade go.qbee.io/transport to 1.26.25 or later.

Summary

go.qbee.io/transport: Symlink-chain path traversal in tar extraction (one level outside destination)

Impact

The go.qbee.io/transport library is affected by a symlink-chain path traversal vulnerability in its extractTar routine. The library's path validation is strictly lexical and fails to account for on-disk symlinks created earlier in the extraction process. Consequently, a crafted tar archive can be used to write or overwrite files one directory level above the intended extraction path. In the case of qbee-agent, which runs with root privileges, this vulnerability permits a root-privileged file write outside the intended destination.

Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.

Affected versions

go.qbee.io/transport (< 1.26.25)

Security releases

go.qbee.io/transport → 1.26.25 (go)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

The issue has been addressed in version v1.26.25

Frequently Asked Questions

What is CVE-2026-55828? CVE-2026-55828 is a medium-severity path traversal vulnerability in go.qbee.io/transport (go), affecting versions < 1.26.25. It is fixed in 1.26.25. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
Which versions of go.qbee.io/transport are affected by CVE-2026-55828? go.qbee.io/transport (go) versions < 1.26.25 is affected.
Is there a fix for CVE-2026-55828? Yes. CVE-2026-55828 is fixed in 1.26.25. Upgrade to this version or later.
Is CVE-2026-55828 exploitable, and should I be worried? Whether CVE-2026-55828 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2026-55828 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2026-55828? Upgrade go.qbee.io/transport to 1.26.25 or later.