# CVE-2026-46410: FileBrowser Quantum: unauthenticated user share share info

> Unauthenticated attackers can access sensitive share information, including source and path details, in FileBrowser Quantum.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 Jul 2026
- **Updated:** 21 Jul 2026
- **Also known as:** GHSA-3jmg-p96m-m328, GO-2026-5089

## What is CVE-2026-46410?

CVE-2026-46410 is a high-severity vulnerability in gtsteffaniak filebrowser, published on 20 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

FileBrowser Quantum is a free, self-hosted, web-based file manager. Versions prior to 1.3.2-stable and 1.4.1-beta may leak some sensitive info, such as source and path. Versions 1.3.2-stable and 1.4.1-beta fix the issue. No known workarounds are available.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

6 open source packages ship an affected version, including github.com/gtsteffaniak/filebrowser and github.com/gtsteffaniak/filebrowser/backend.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/gtsteffaniak/filebrowser` | Go | All versions | 1.2.1-stable.0.20260514154726-1802e1281135 |
| `github.com/gtsteffaniak/filebrowser` | Go | All versions | 1.2.1-stable.0.20260514154726-1802e1281135 |
| `github.com/gtsteffaniak/filebrowser` | Go | All versions | 1.2.1-stable.0.20260514154726-1802e1281135 |
| `github.com/gtsteffaniak/filebrowser/backend` | Go | All versions | 0.0.0-20260514154726-1802e1281135 |
| `github.com/gtsteffaniak/filebrowser/backend` | Go | All versions | 0.0.0-20260514154726-1802e1281135 |
| `github.com/gtsteffaniak/filebrowser/backend` | Go | All versions | 0.0.0-20260514154726-1802e1281135 |

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

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

## Is CVE-2026-46410 being exploited?

There is no known exploitation of CVE-2026-46410 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-46410 is a high-severity vulnerability in gtsteffaniak filebrowser, published on 20 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-46410 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/gtsteffaniak/filebrowser (Go): affected all versions; fixed in 1.2.1-stable.0.20260514154726-1802e1281135
- github.com/gtsteffaniak/filebrowser (Go): affected all versions; fixed in 1.2.1-stable.0.20260514154726-1802e1281135
- github.com/gtsteffaniak/filebrowser (Go): affected all versions; fixed in 1.2.1-stable.0.20260514154726-1802e1281135
- github.com/gtsteffaniak/filebrowser/backend (Go): affected all versions; fixed in 0.0.0-20260514154726-1802e1281135
- github.com/gtsteffaniak/filebrowser/backend (Go): affected all versions; fixed in 0.0.0-20260514154726-1802e1281135
- github.com/gtsteffaniak/filebrowser/backend (Go): affected all versions; fixed in 0.0.0-20260514154726-1802e1281135

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

## Sources

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

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