Venice vulnerable to Partial Path Traversal issue within the functions load-file and load-resource

Exploitation

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

CVSS

6.1 · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N

EPSS

• CVE-2022-36007: 0.43% estimated exploitation activity in the next 30 days; percentile 37.33 (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.

Impact A partial path traversal issue exists within the functions load-file and load-resource. These functions can be limited to load files from a list of load paths. Assuming Venice has been configured with the load paths: [ "/Users/foo/resources" ] When passing relative paths to these two vulnerable functions everything is fine: (load-resource "test.png") = loads the file "/Users/foo/resources/test.png" (load-resource "../resources-alt/test.png") = rejected, outside the load path When passing absolute paths to these two vulnerable functions Venice may return files outside the configured load paths: (load-resource "/Users/foo/resources/test.png") = loads the file "/Users/foo/resources/test.png" (load-resource "/Users/foo/resources-alt/test.png") = loads the file "/Users/foo/resources-alt/test.png" !!! The latter call suffers from the Partial Path Traversal vulnerability. This issue’s scope is limited to absolute paths whose name prefix matches a load path. E.g. for a load-path…

Published by the source

18 Aug 2022, 19:07 UTC

Last modified by the source

30 Jan 2023, 05:07 UTC

Source last checked

26 Oct 2026, 16:02 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-4mmh-5vw7-rgvj

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

# Patch Next advisory brief: CVE-2022-36007

Advisory: Venice vulnerable to Partial Path Traversal issue within the functions `load-file` and `load-resource`
IDs: CVE-2022-36007, GHSA-4mmh-5vw7-rgvj
Record: https://patchnext.com/advisories/cve-2022-36007 (revision 1, source checked 26 Oct 2026, 16:02 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: com.github.jlangch:venice 1.10.17. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven com.github.jlangch:venice: affected <= 1.10.16; fixed in 1.10.17

## Suggested inspection (read-only)
- Maven com.github.jlangch:venice: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on com.github.jlangch:venice.
- 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-4mmh-5vw7-rgvj (GitHub-reviewed advisory GHSA-4mmh-5vw7-rgvj lists affected ranges: Maven com.github.jlangch:venice >=0 <=1.10.16)

Commands are suggestions: review each one before running it.