Vulnerability in github.com/candid82/joker (CVE-2026-59172)
Summary
Vulnerability in github.com/candid82/joker (CVE-2026-59172). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.8.2 or later.
Original description
The description as published by the source.
Impact
In Joker versions before 1.8.2, joker --lint 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).
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-59172 has been found in github.com/candid82/joker.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/candid82/joker to 1.8.2 or later.
If unsure, ask your IT team or search "github.com/candid82/joker CVE-2026-59172" on the vendor's site.
CVE-2026-59172 (github.com/candid82/joker) — CWE-829
Patched: 1.8.2 — apply immediately
Workaround: Users who cannot upgrade should avoid running joker --lint on untrusted repositories, especially through editor integrations or unattended CI.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-829) exists in github.com/candid82/joker.
Check the vendor advisory for the affected versions of github.com/candid82/joker.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.8.2.
Workaround: Users who cannot upgrade should avoid running joker --lint on untrusted repositories, especially through editor integrations or unattended CI.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/candid82/joker' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/candid82/joker' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/candid82/jokerを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Users who cannot upgrade should avoid running `joker --lint` on untrusted repositories, especially through editor integrations or unattended CI.パッチが適用されるまでの応急処置として、Users who cannot upgrade should avoid running
joker --linton untrusted repositories, especially through editor integrations or unattended CI. を実施。回避策の副作用 (機能低下) を確認した上で。 -
3Apply patch patch
Upgrade github.com/candid82/joker to 1.8.2ステージング環境で 1.8.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- web github.com
- web github.com