<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Thu, 29 Oct 2026 18:52:21 +0000</lastBuildDate>
    <item>
      <title>GHSA-m835-3cm9-rggg — Joker linter executed project-local .jokerd/linter.* files during linting</title>
      <link>https://db.gcve.eu/vuln/ghsa-m835-3cm9-rggg</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/candid82/joker&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;In Joker versions before 1.8.2, `joker --lint &amp;lt;file&amp;gt;` 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.&lt;/p&gt;
&lt;p&gt;This could be triggered by editor integrations or CI jobs that automatically run `joker --lint` on checked-out source code.&lt;/p&gt;
&lt;p&gt;## Patches&lt;/p&gt;
&lt;p&gt;Fixed in Joker v1.8.2. Executable linter customization files are now loaded only from the user&amp;#39;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.&lt;/p&gt;
&lt;p&gt;## Workarounds&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;## Credits&lt;/p&gt;
&lt;p&gt;Reported by Younghun Ko of AhnLab (@koyokr).&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/candid82/joker&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;In Joker versions before 1.8.2, `joker --lint &amp;lt;file&amp;gt;` 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.&lt;/p&gt;
&lt;p&gt;This could be triggered by editor integrations or CI jobs that automatically run `joker --lint` on checked-out source code.&lt;/p&gt;
&lt;p&gt;## Patches&lt;/p&gt;
&lt;p&gt;Fixed in Joker v1.8.2. Executable linter customization files are now loaded only from the user&amp;#39;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.&lt;/p&gt;
&lt;p&gt;## Workarounds&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;## Credits&lt;/p&gt;
&lt;p&gt;Reported by Younghun Ko of AhnLab (@koyokr).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-m835-3cm9-rggg</guid>
    </item>
  </channel>
</rss>
