Joker linter executed project-local .jokerd/linter.* files during linting (CVE-2026-59172) | HOL Guard CVE

High · CVSS 7.8CVE-2026-59172GHSA-M835-3CM9-RGGG

Joker linter executed project-local .jokerd/linter.* files during linting

Answer in brief

CVE-2026-59172 records a High severity (CVSS 7.8) vulnerability in Joker linter executed project-local .jokerd/linter.* files during linting. The current sources do not mark it as known exploited. The current feed maps github.com/candid82/joker (go), github.com/candid82/joker (go). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 9, 2026Updated Sep 10, 2026Source checked Sep 10, 2026First seen by HOL Sep 9, 2026Material review Sep 10, 2026

Upstream Advisory

Key facts

Risk: High · CVSS 7.8
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps github.com/candid82/joker (go), github.com/candid82/joker (go). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
github.com/candid82/jokergo	<1.8.2	1.8.2
github.com/candid82/jokergo	>=0 <1.8.2	1.8.2

Recommended response

Check inventory. Check lockfiles and deployed manifests for github.com/candid82/joker, github.com/candid82/joker.
Review the reported fix. Update github.com/candid82/joker to 1.8.2; github.com/candid82/joker to 1.8.2 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 9, 2026
Evidence: source:ghsa:source_dates:source-dates:record
Source modified
Sep 10, 2026
Evidence: source:ghsa:source_dates:source-dates:record
First seen by HOL
Sep 9, 2026

Sources and claim methodology

Upstream source description

## Impact In Joker versions before 1.8.2, `joker --lint <file>` located a `.jokerd/` directory by walking up from the linted file and executed matching `linter.*` files from that directory before linting. Because these files are executable Joker/Clojure code, linting a file inside an untrusted repository could execute code supplied by that repository. This could be triggered by editor integrations or CI jobs that automatically run `joker --lint` on checked-out source code. ## Patches Fixed in Joker v1.8.2. Executable linter customization files are now loaded only from the user's home `.jokerd` directory (`~/.jokerd/linter.cljc`, `~/.jokerd/linter.clj`, `~/.jokerd/linter.cljs`, or `~/.jokerd/linter.joke`). Project-local `.jokerd/linter.*` files are no longer executed. ## Workarounds Users who cannot upgrade should avoid running `joker --lint` on untrusted repositories, especially through editor integrations or unattended CI. Removing or disabling project-local `.jokerd/linter.*` files before linting also avoids the code-execution path. ## Credits Reported by Younghun Ko of AhnLab (@koyokr).

Quoted source text, attributed separately from HOL analysis.