Directory Traversal Affecting gitlab-rails-ce-19.1 package, versions <19.1.9-r0


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.5% (43rd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-CHAINGUARDLATEST-GITLABRAILSCE191-21689133
  • published24 Oct 2026
  • disclosed20 Oct 2026

Introduced: 20 Oct 2026

NewCVE-2026-112947  (opens in a new tab)
CWE-22  (opens in a new tab)
CWE-200  (opens in a new tab)
CWE-209  (opens in a new tab)

How to fix?

Upgrade Chainguard gitlab-rails-ce-19.1 to version 19.1.9-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream gitlab-rails-ce-19.1 package and not the gitlab-rails-ce-19.1 package as distributed by Chainguard. See How to fix? for Chainguard relevant fixed versions and status.

Vite is a frontend tooling framework for JavaScript. From 8.2.0 until 8.2.4 and 8.3.3, the first 4 bytes of files outside of server.fs setting can be returned to the browser by a request containing ?vite-wasm-instance. Requests containing the ?vite-wasm-instance query are handled by the internal Wasm plugin's load hook. The hook removes the query and reads the resulting path directly from disk, but the server.fs checks were not applied. After reading the file, Vite attempts to parse it as WebAssembly. When that parse fails, Node and deno throws an error that contains the first 4 bytes of the file. This vulnerability is fixed in 8.2.4 and 8.3.3.

CVSS Base Scores

version 3.1