# filebrowser Sets Insecure File Permissions in github.com/filebrowser/filebrowser

Advisory record · `GHSA-jj2r-455p-5gvf`

- **Identifiers:** `GHSA-jj2r-455p-5gvf` · `CVE-2025-52900` · `GO-2025-3785`
- **State:** Confirmed
- **Severity:** CVSS 5.5 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-276](https://cwe.mitre.org/data/definitions/276.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 28 Jul 2025
- **Updated:** 3 Mar 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 28 Jul 2025, 19:57 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `github.com/filebrowser/filebrowser` (Go): affected `all versions`; no fixed version yet
- `github.com/filebrowser/filebrowser/v2` (Go): affected `<2.33.7`; fixed in `2.33.7`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Filebrowser's v2 module (github.com/filebrowser/filebrowser/v2) before 2.33.7 sets insecure file permissions, according to the advisory. The source gives few details about who can exploit this or what they can access. Upgrade github.com/filebrowser/filebrowser/v2 to 2.33.7 or later; no fixed version is listed for the unversioned github.com/filebrowser/filebrowser package.

Written 10 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 5.5 Medium, CVSS 3.1: `CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0022, the 13th percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the GitHub Advisory Database, published 28 Jul 2025. New records show when each source confirmed them.

## Sources

- [GitHub Advisory Database: GHSA-jj2r-455p-5gvf](https://github.com/advisories/GHSA-jj2r-455p-5gvf)
- [OSV: GHSA-jj2r-455p-5gvf](https://osv.dev/vulnerability/GHSA-jj2r-455p-5gvf)
- <https://github.com/filebrowser/filebrowser/security/advisories/GHSA-jj2r-455p-5gvf>
- <https://nvd.nist.gov/vuln/detail/CVE-2025-52900>
- <https://github.com/filebrowser/filebrowser/commit/ca86f916216620365c0f81629c0934ce02574d76>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-jj2r-455p-5gvf>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-jj2r-455p-5gvf/>. Everything for agents: <https://agentprime.io/llms.txt>.
