# CVE-2026-59172: Joker linter executed project-local .jokerd/linter.* files during linting


- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 28 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-m835-3cm9-rggg, GO-2026-6450

## What is CVE-2026-59172?

CVE-2026-59172 is a high-severity vulnerability in candid82 joker, published on 28 Oct 2026. 

### Official description

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.

Weakness: CWE-829 (Inclusion of Functionality from Untrusted Control Sphere)

## Which versions are affected by CVE-2026-59172?

3 open source packages ship an affected version, including github.com/candid82/joker.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/candid82/joker` | Go | All versions | 1.8.2 |
| `github.com/candid82/joker` | Go | All versions | 1.8.2 |
| `github.com/candid82/joker` | Go | All versions | 1.8.2 |

## How do I fix CVE-2026-59172?

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

## Is CVE-2026-59172 being exploited?

There is no known exploitation of CVE-2026-59172 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-59172 and fix it if it is affected.

What it is: CVE-2026-59172 is a high-severity vulnerability in candid82 joker, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-59172 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/candid82/joker (Go): affected all versions; fixed in 1.8.2
- github.com/candid82/joker (Go): affected all versions; fixed in 1.8.2
- github.com/candid82/joker (Go): affected all versions; fixed in 1.8.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-59172/ (Markdown: https://insights.sbomify.com/CVE-2026-59172/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-59172
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-59172
- OSV: https://osv.dev/vulnerability/CVE-2026-59172

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-59172/
Summaries are generated and may contain mistakes; the official description above is the record.