Live › vulnerability › CVE-2026-59172
Go to dashboardJoker's `--lint` mode searches parent directories for a `.jokerd/` folder and runs any `linter.*` files it finds before linting. A malicious repository can ship such files, so linting a checked-out file runs the attacker's code with the linter user's privileges.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-28 14:33 UTC. All times on this page are UTC.
Teams that run Joker's linter on source code they did not write, such as editor integrations linting files on open or CI jobs linting pull request checkouts. Exposure depends on the linter running against untrusted trees; projects that only lint their own trusted code have less exposure. Users who never run Joker can skip it.
No product ranges from the sources yet.
joker --version and confirm it reports a version below 1.8.2.joker --lint on checked-out source from untrusted repositories.1.8.2 or later, which loads executable customization only from the user's home directory.joker --lint on files from untrusted repositories.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Joker is a small Clojure interpreter, linter and formatter written in Go. Prior to 1.8.2, joker --lint <file> walks upward from the linted file to locate a .jokerd/ directory and executes matching linter.* files before linting. Those files contain executable Joker/Clojure code, so linting a file inside an untrusted repository can execute repository-supplied code with the linter user's privileges. Editor integrations and CI jobs that automatically lint checked-out source can trigger this behavior. The patch stops executing project-local linter customizations and loads executable customization only from the user's home directory. This issue is fixed in version 1.8.2.
This page as .md · .json · in your agent: get_signal("CVE-2026-59172")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.