Bug 2528152 - CVE-2026-84373 forgejo: Vitest: Arbitrary File Read via Path Traversal in HMR WebSocket [epel-all]
Summary: CVE-2026-84373 forgejo: Vitest: Arbitrary File Read via Path Traversal in HMR...
Keywords:
Status: NEW
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: forgejo
Version: epel10
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Fedora Infrastructure SIG
QA Contact:
URL:
Whiteboard: {"flaws": ["3fbd19a1-248f-4ca4-b846-2...
Depends On:
Blocks: CVE-2026-84373
TreeView+ depends on / blocked
 
Reported: 2026-09-03 17:38 UTC by Ganesh
Modified: 2026-09-03 17:38 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Ganesh 2026-09-03 17:38:50 UTC
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.

Vitest is a testing framework powered by Vite. From 2.1.0 until 4.1.11 and 5.0.0-rc.2, the public mockerPlugin and standalone interceptorPlugin exports in packages/mocker/src/node/interceptorPlugin.ts register the vitest:interceptor:register handler on Vite's unauthenticated HMR WebSocket without validating redirect targets against the file-serving allowlist. The implementation processes event.redirect without enforcing server.fs.allow and server.fs.deny through isFileLoadingAllowed. A remote client that can reach an exposed development server can submit an opaque URL scheme preserving .. segments, causing join(server.config.root, redirectUrl.pathname) to resolve outside the project root. The plugin's load hook then returns readFile(mock.redirect, 'utf-8') as module source, disclosing local files readable by the dev-server process. Vitest browser mode uses a token-authenticated RPC and is not remotely unauthenticated by default, although the same boundary check was missing on that path. This issue is fixed in versions 4.1.11 and 5.0.0-rc.2.


Note You need to log in before you can comment on or make changes to this bug.