How severe is GHSA-3jmg-p96m-m328?

No CVSS score has been assigned to GHSA-3jmg-p96m-m328 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-3jmg-p96m-m328?

GHSA-3jmg-p96m-m328 affects the following packages: github.com/gtsteffaniak/filebrowser/backend (Go), github.com/gtsteffaniak/filebrowser (Go). Ecosystems affected: Go.

How do I fix GHSA-3jmg-p96m-m328?

Update github.com/gtsteffaniak/filebrowser/backend to 0.0.0-20260514154726-1802e1281135 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3jmg-p96m-m328 is resolved across your whole dependency graph.

How do I detect GHSA-3jmg-p96m-m328 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/gtsteffaniak/filebrowser/backend, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-3jmg-p96m-m328 if there is no patch (or I can't update yet)?

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is GHSA-3jmg-p96m-m328 actively exploited in the wild?

No public exploit code has been indexed for GHSA-3jmg-p96m-m328 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 is the EPSS score for GHSA-3jmg-p96m-m328?

GHSA-3jmg-p96m-m328 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 36th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-3jmg-p96m-m328?

GHSA-3jmg-p96m-m328 is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-3jmg-p96m-m328 published, and has it been updated?

GHSA-3jmg-p96m-m328 was published on May 19, 2026 and was last updated on June 25, 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

Not in CISA KEV

GHSA-3jmg-p96m-m328 — backend

Fix: gtsteffaniak/filebrowser@1802e12

GHSA-3jmg-p96m-m328 is a Information Exposure vulnerability in github.com/gtsteffaniak/filebrowser/backend. A fix is available for github.com/gtsteffaniak/filebrowser/backend — see the affected versions and patch details below.

FileBrowser Quantum: unauthenticated user share share info

Also known asCVE-2026-46410GO-2026-5089

Published

May 19, 2026

Updated

Jun 25, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Oct 1, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-3jmg-p96m-m328.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs36th percentile — riskier than 36% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

2 pkgs affected

🐹github.com/gtsteffaniak/filebrowser/backend🐹github.com/gtsteffaniak/filebrowser

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

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.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/gtsteffaniak/filebrowser/backend`	all versions	0.0.0-20260514154726-1802e1281135`go get github.com/gtsteffaniak/filebrowser/backend@v0.0.0-20260514154726-1802e1281135`
🐹Go	`github.com/gtsteffaniak/filebrowser`	all versions	1.2.1-stable.0.20260514154726-1802e1281135`go get github.com/gtsteffaniak/filebrowser@v1.2.1-stable.0.20260514154726-1802e1281135`

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/gtsteffaniak/filebrowser/backend, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/gtsteffaniak/filebrowser/backend to 0.0.0-20260514154726-1802e1281135 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3jmg-p96m-m328 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Frequently Asked Questions

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

O3 Security · Impact-Aware SCA

Is GHSA-3jmg-p96m-m328 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works