CVE-2026-59172: Github.com/candid82/joker Joker Linter Executed Project-local .jokerd/linter.* Vulnerability

HIGH
Advisory Identifier: GHSA-m835-3cm9-rggg
CVSS 7.8
CWE-829
Published
Advisory Summary

CVE-2026-59172 is a HIGH (CVSS 7.8) joker linter executed project-local .jokerd/linter.* vulnerability (CWE-829: Inclusion of Functionality from Untrusted Control Sphere) affecting Github.com/candid82/joker libraries in the Go ecosystem. The issue involves joker linter executed project-local .jokerd/linter.* files during linting. Remediation is available by upgrading affected packages to version 1.8.2.

CVE-2026-59172 at a Glance

CVE Identifier CVE-2026-59172
GHSA Identifier GHSA-m835-3cm9-rggg
Severity HIGH
CVSS v3.1 Base Score 7.8
CWE Classification CWE-829: Inclusion of Functionality from Untrusted Control Sphere
Affected Product Github.com/candid82/joker
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 7.8

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H).

Attack Vector Local (AV:L)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction Required (UI:R)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2026-59172

To remediate this vulnerability, upgrade all affected Github.com/candid82/joker dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/candid82/joker fixed: 1.8.2
Upgrade github.com/candid82/joker to 1.8.2
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/candid82/joker

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-59172, inspect your project dependencies for Github.com/candid82/joker:

inspect dependencies for github.com/candid82/joker

Analyze the terminal output to locate any version of Github.com/candid82/joker in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.8.2), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-829: Inclusion of Functionality from Untrusted Control Sphere, where the product imports, requires, or includes executable functionality (such as a library) from a source that is outside of the intended control sphere. In Github.com/candid82/joker, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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

CVE-2026-59172 Affected Github.com/candid82/joker Versions

1 component(s)
Fixed Versions:
1.8.2
Product / Package Ecosystem Affected Versions Fixed Version
github.com/candid82/joker
Go
< 1.8.2
1.8.2

References

Frequently Asked Questions

What is CVE-2026-59172?
CVE-2026-59172 is a security vulnerability in Github.com/candid82/joker involving Joker linter executed project-local .jokerd/linter.* files during linting under CWE-829: Inclusion of Functionality from Untrusted Control Sphere.
Which Github.com/candid82/joker versions are affected?
Affected versions include releases prior to 1.8.2 across affected packages: github.com/candid82/joker.
What version fixes CVE-2026-59172?
Upgrading to 1.8.2 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/candid82/joker affected?
Yes, github.com/candid82/joker is affected in releases prior to 1.8.2. Upgrade your dependency to 1.8.2 or later.
What is the CVSS score of CVE-2026-59172?
CVE-2026-59172 has a CVSS v3.1 base score of 7.8 (HIGH) with vector string CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2026-59172?
CVE-2026-59172 is classified under CWE-829: Inclusion of Functionality from Untrusted Control Sphere (The product imports, requires, or includes executable functionality (such as a library) from a source that is outside of the intended control sphere.).
How can I check Go dependencies for CVE-2026-59172?
Run the dependency tree command: 'inspect dependencies for github.com/candid82/joker'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-m835-3cm9-rggg",
  "modified" : "2026-09-09T23:48:46Z",
  "published" : "2026-09-09T23:48:46Z",
  "aliases" : [ "CVE-2026-59172" ],
  "summary" : "Joker linter executed project-local .jokerd/linter.* files during linting",
  "details" : "## Impact\n\nIn 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.\n\nThis could be triggered by editor integrations or CI jobs that automatically run `joker --lint` on checked-out source code.\n\n## Patches\n\nFixed 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.\n\n## Workarounds\n\nUsers 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.\n\n## Credits\n\nReported by Younghun Ko of AhnLab (@koyokr).",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/candid82/joker"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.8.2"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/candid82/joker/security/advisories/GHSA-m835-3cm9-rggg"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/candid82/joker"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-829" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-09-09T23:48:46Z",
    "nvd_published_at" : null
  }
}