Directory Traversal Affecting gitlab-rails-ce-19.5 package, versions <19.5.1-r1


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.85% (58th 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-GITLABRAILSCE195-21663401
  • published23 Oct 2026
  • disclosed20 Oct 2026

Introduced: 20 Oct 2026

NewCVE-2026-112946  (opens in a new tab)
CWE-22  (opens in a new tab)
CWE-284  (opens in a new tab)

How to fix?

Upgrade Chainguard gitlab-rails-ce-19.5 to version 19.5.1-r1 or higher.

NVD Description

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

Vite is a frontend tooling framework for JavaScript. Prior to 6.4.4, 7.3.7, 8.1.6, 8.2.4, and 8.3.3, import analysis can record a root-relative browser URL in safeModulePaths instead of the cleaned resolved module identifier. On a network-accessible, non-Windows development server, an imported project file whose URL matches an absolute host path can authorize a later raw-filesystem request for that host file, provided server.fs.deny does not block it. The request can disclose the matching file outside the project root, but it does not allow arbitrary path traversal because the host path must correspond to a project-relative URL authorized by the application graph. This issue is fixed in versions 6.4.4, 7.3.7, 8.1.6, 8.2.4, and 8.3.3.

CVSS Base Scores

version 3.1