{"vulnerability": "CVE-2022-36007", "sightings": [{"uuid": "8fc64b5d-feed-4a87-beed-c503f73eeaa3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-36007", "type": "seen", "source": "https://bsky.app/profile/beikokucyber.bsky.social/post/3lwze4vmdvk26", "content": "", "creation_timestamp": "2025-08-22T21:02:31.672825Z"}, {"uuid": "d87d96d9-aed6-4cc6-a444-951c0865e578", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-36007", "type": "seen", "source": "https://t.me/cibsecurity/48139", "content": "\u203c CVE-2022-36007 \u203c\n\nVenice is a Clojure inspired sandboxed Lisp dialect with excellent Java interoperability. 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\")` =&gt; loads the file \"/Users/foo/resources/test.png\" `(load-resource \"../resources-alt/test.png\")` =&gt; 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\")` =&gt; loads the file \"/Users/foo/resources/test.png\" `(load-resource \"/Users/foo/resources-alt/test.png\")` =&gt; loads the file \"/Users/foo/resources-alt/test.png\" !!! The latter call suffers from the _Partial Path Traversal_ vulnerability. This issue\u00e2\u20ac\u2122s scope is limited to absolute paths whose name prefix matches a load path. E.g. for a load-path `\"/Users/foo/resources\"`, the actor can cause loading a resource also from `\"/Users/foo/resources-alt\"`, but not from `\"/Users/foo/images\"`. Versions of Venice before and including v1.10.17 are affected by this issue. Upgrade to Venice &gt;= 1.10.18, if you are on a version &lt; 1.10.18. There are currently no known workarounds.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2022-08-15T14:37:55.000000Z"}, {"uuid": "8a6b3103-9ad9-4493-bfa5-e17d8836a10f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-36007", "type": "seen", "source": "Telegram/DGzHuk8RVb1b8Xt8T_i7JrWo03tk4z5tw950ouDC7Dv-DN4", "content": "", "creation_timestamp": "2026-09-04T18:00:04.000683Z"}, {"uuid": "8a08e226-d6b4-44ba-aaa0-152ac1cf00a3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-36007", "type": "published-proof-of-concept", "source": "Telegram/DGzHuk8RVb1b8Xt8T_i7JrWo03tk4z5tw950ouDC7Dv-DN4", "content": "", "creation_timestamp": "2026-09-05T01:00:20.559993Z"}]}