github.com/gtsteffaniak/filebrowser/backend

CVE-2026-46410

CVE-2026-46410 is a high-severity security vulnerability in github.com/gtsteffaniak/filebrowser/backend (go), affecting versions < 0.0.0-20260514154726-1802e1281135. It is fixed in 0.0.0-20260514154726-1802e1281135, 1.2.1-stable.0.20260514154726-1802e1281135.

Key facts
CVSS score
N/A
High
Attack vector
Not available
Issuing authority
GitHub Advisory Database
Affected package
github.com/gtsteffaniak/filebrowser/backend
Fixed in
0.0.0-20260514154726-1802e1281135, 1.2.1-stable.0.20260514154726-1802e1281135
Disclosed
2026

Summary

Impact Some sensitive info -- such as source and path can get exposed. Patches Update to the latest version Workarounds no

Impact

Not available

Affected versions

go

  • github.com/gtsteffaniak/filebrowser/backend (< 0.0.0-20260514154726-1802e1281135)
  • github.com/gtsteffaniak/filebrowser (< 1.2.1-stable.0.20260514154726-1802e1281135)

Security releases

  • github.com/gtsteffaniak/filebrowser/backend → 0.0.0-20260514154726-1802e1281135 (go)
  • github.com/gtsteffaniak/filebrowser → 1.2.1-stable.0.20260514154726-1802e1281135 (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 instead of chasing every advisory.

Kodem's runtime-powered SCA identifies whether CVE-2026-46410 is reachable in your applications. Explore open-source security for your team.

See if CVE-2026-46410 is reachable in your applications. Get a demo

Already deployed Kodem? See CVE-2026-46410 in your environment

Remediation advice

Upgrade the following packages to resolve this vulnerability:

  • Upgrade github.com/gtsteffaniak/filebrowser/backend to 0.0.0-20260514154726-1802e1281135 or later
  • Upgrade github.com/gtsteffaniak/filebrowser to 1.2.1-stable.0.20260514154726-1802e1281135 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently asked questions about CVE-2026-46410

What is CVE-2026-46410?

CVE-2026-46410 is a high-severity security vulnerability in github.com/gtsteffaniak/filebrowser/backend (go), affecting versions < 0.0.0-20260514154726-1802e1281135. It is fixed in 0.0.0-20260514154726-1802e1281135, 1.2.1-stable.0.20260514154726-1802e1281135.

Which packages are affected by CVE-2026-46410?
  • github.com/gtsteffaniak/filebrowser/backend (go) (versions < 0.0.0-20260514154726-1802e1281135)
  • github.com/gtsteffaniak/filebrowser (go) (versions < 1.2.1-stable.0.20260514154726-1802e1281135)
Is there a fix for CVE-2026-46410?

Yes. CVE-2026-46410 is fixed in 0.0.0-20260514154726-1802e1281135, 1.2.1-stable.0.20260514154726-1802e1281135. Upgrade to this version or later.

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

Whether CVE-2026-46410 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-46410 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-46410?
  • Upgrade github.com/gtsteffaniak/filebrowser/backend to 0.0.0-20260514154726-1802e1281135 or later
  • Upgrade github.com/gtsteffaniak/filebrowser to 1.2.1-stable.0.20260514154726-1802e1281135 or later

Stop the waste.
Protect your environment with Kodem.