File Browser's Uncontrolled Memory Consumption vulnerability can enable DoS attack due to oversized file processing

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

7.7 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:P · score source

EPSS

• CVE-2025-53893: 0.41% estimated exploitation activity in the next 30 days; percentile 34.89 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary A Denial of Service (DoS) vulnerability exists in the file processing logic when reading a file on endpoint Filebrowser-Server-IP:PORT/files/{file-name} . While the server correctly handles and stores uploaded files, it attempts to load the entire content into memory during read operations without size checks or resource limits. This allows an authenticated user to upload a large file and trigger uncontrolled memory consumption on read, potentially crashing the server and making it unresponsive. Details The endpoint /api/resources/{file-name} accepts PUT requests with plain text file content. Uploading an extremely large file (e.g., ~1.5 GB) succeeds without issue. However, when the server attempts to open and read this file, it performs the read operation in an unbounded or inefficient way, leading to excessive memory usage. This approach attempts to read the entire file into memory at once. For large files, this causes memory exhaustion resulting in a crash or serious…

Published by the source

16 Jul 2025, 14:22 UTC

Last modified by the source

29 Jul 2025, 23:27 UTC

Source last checked

26 Oct 2026, 15:09 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-7xqm-7738-642x

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-53893

Advisory: File Browser's Uncontrolled Memory Consumption vulnerability can enable DoS attack due to oversized file processing
IDs: CVE-2025-53893, GHSA-7xqm-7738-642x
Record: https://patchnext.com/advisories/cve-2025-53893 (revision 1, source checked 26 Oct 2026, 15:09 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/filebrowser/filebrowser/v2: affected >= 2.38.0, <= 2.38.0

## Suggested inspection (read-only)
- Go github.com/filebrowser/filebrowser/v2: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/filebrowser/filebrowser/v2.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-7xqm-7738-642x (GitHub-reviewed advisory GHSA-7xqm-7738-642x lists affected ranges: Go github.com/filebrowser/filebrowser/v2 >=2.38.0 <=2.38.0)

Commands are suggestions: review each one before running it.