What is CVE-2026-59172?

CVE-2026-59172 is a high-severity security vulnerability in github.com/candid82/joker (go), affecting versions < 1.8.2. It is fixed in 1.8.2.

How severe is CVE-2026-59172?

CVE-2026-59172 has a CVSS score of 7.8 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of github.com/candid82/joker are affected by CVE-2026-59172?

github.com/candid82/joker (go) versions < 1.8.2 is affected.

Is there a fix for CVE-2026-59172?

Yes. CVE-2026-59172 is fixed in 1.8.2. Upgrade to this version or later.

Is CVE-2026-59172 exploitable, and should I be worried?

Whether CVE-2026-59172 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2026-59172 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2026-59172?

Upgrade github.com/candid82/joker to 1.8.2 or later.

CVE-2026-59172 in github.com/candid82/joker

Q: How severe is CVE-2026-59172?

CVE-2026-59172 has a CVSS score of 7.8 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of github.com/candid82/joker are affected by CVE-2026-59172?

github.com/candid82/joker (go) versions < 1.8.2 is affected.

Q: Is there a fix for CVE-2026-59172?

Yes. CVE-2026-59172 is fixed in 1.8.2. Upgrade to this version or later.

Q: Is CVE-2026-59172 exploitable, and should I be worried?

Whether CVE-2026-59172 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2026-59172 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2026-59172?

Upgrade github.com/candid82/joker to 1.8.2 or later.

Summary

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

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).

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.

CVE-2026-59172 has a CVSS score of 7.8 (High). The vector is requires local access, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.8.2); upgrading removes the vulnerable code path.

Affected versions

github.com/candid82/joker (< 1.8.2)

Security releases

github.com/candid82/joker → 1.8.2 (go)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

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.

Frequently Asked Questions

What is CVE-2026-59172? CVE-2026-59172 is a high-severity security vulnerability in github.com/candid82/joker (go), affecting versions < 1.8.2. It is fixed in 1.8.2.
How severe is CVE-2026-59172? CVE-2026-59172 has a CVSS score of 7.8 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of github.com/candid82/joker are affected by CVE-2026-59172? github.com/candid82/joker (go) versions < 1.8.2 is affected.
Is there a fix for CVE-2026-59172? Yes. CVE-2026-59172 is fixed in 1.8.2. Upgrade to this version or later.
Is CVE-2026-59172 exploitable, and should I be worried? Whether CVE-2026-59172 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2026-59172 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2026-59172? Upgrade github.com/candid82/joker to 1.8.2 or later.