On this page (7 sections)

On November 4, 2026, Debian published DSA-6609-1, a security update for trapperkeeper-authorization-clojure. Debian describes Trapperkeeper as a service framework used by Puppet servers. According to the advisory, incorrect validation of hostname access control lists (ACLs) in its authorization service could allow a Puppet client to download the catalogue of a different host.

If you run a Puppet server on Debian 13 (trixie), or manage one for clients, this is worth a quick check. The advisory is short and several details are not public, so this article separates what Debian has confirmed from what is still unknown.

What Debian has confirmed

The advisory states one problem: hostname ACLs are validated incorrectly in the Trapperkeeper authorization service. The stated impact is that a Puppet client could download the catalogue of a different host. Debian recommends upgrading the trapperkeeper-authorization-clojure packages and points to its security tracker page for the detailed status.

The fix is listed only for the stable distribution, trixie, in version 2.0.1-2+deb13u1. The advisory does not mention other Debian releases, so we cannot say whether they are affected or not.

Why a catalogue leak matters

A Puppet catalogue is the compiled set of configuration that the server computes for one specific node. Depending on how your manifests are written, it can contain file contents, package and service definitions, user accounts, internal hostnames and sometimes secrets passed as parameters. Puppet servers normally decide which client may fetch which catalogue by checking the requesting client's identity against authorization rules.

This weakness class is an access control validation error. When a hostname rule is matched incorrectly, a client may be treated as allowed to read data meant for another node. The advisory does not say how the mismatch can be triggered, and we are not going to speculate about it. What matters for planning is the impact: confidentiality of other nodes' configuration data.

What is not known yet

  • No CVE identifier had been assigned when the advisory was issued, so there is no NVD record or CVSS score to quote.
  • The advisory does not say whether the issue has been exploited. We have no information either way.
  • It does not describe whether a client needs a valid certificate to attempt this. Until you know more, treat any enrolled or reachable client as a potential source.
  • It does not state which versions before the fixed one are affected.
  • Only one publisher, Debian itself, covers this story so far, so there is no second-source confirmation of the details.
We will not assign a severity to this issue. Rate it yourself based on what your catalogues contain and who can connect to your Puppet server.

Who is realistically exposed

Exposure is most likely limited to environments that run a Puppet server on Debian trixie with this package installed. Typical cases are internal infrastructure teams, hosting providers and agencies that manage fleets of servers with Puppet. A single-site owner on shared hosting is unlikely to run this software.

The risk is higher if your catalogues include sensitive values, if many different teams or customers have nodes enrolled against one Puppet server, or if the server is reachable from less trusted networks.

How to check your exposure

On a Debian host that may run the Puppet server, this read-only command shows whether the package is installed and which version. Compare any version it prints with 2.0.1-2+deb13u1:

Show the installed package version (Debian)Shell
dpkg -l trapperkeeper-authorization-clojure

This read-only command shows the installed version and the candidate version from your configured repositories, so you can see whether the fixed version is available:

Compare installed and candidate versions (Debian)Shell
apt-cache policy trapperkeeper-authorization-clojure

If the installed version on trixie is older than 2.0.1-2+deb13u1, plan the update. If the package is not installed on a host, this advisory is not relevant to that host. For other Debian releases, consult the Debian security tracker, since the advisory is silent on them.

What to do now

Debian's advisory only recommends upgrading the trapperkeeper-authorization-clojure packages. The command below is standard Debian practice for upgrading a single installed package and is not taken from the advisory. It refreshes the package lists and upgrades only this package, if it is already installed (run as root):

Upgrade just this package (Debian, run as root)Shell
apt-get update && apt-get install --only-upgrade trapperkeeper-authorization-clojure
Caution. A running service usually needs a restart to load updated code, and the advisory does not say whether one is needed here. Check how your Puppet server is deployed and plan any restart in a maintenance window, because nodes may be unable to fetch catalogues while the service restarts.
  1. Identify every Debian 13 (trixie) host that runs a Puppet server.
  2. Check the installed version of trapperkeeper-authorization-clojure and compare it with 2.0.1-2+deb13u1.
  3. Upgrade the package with your normal Debian update process (for example the command above).
  4. Restart the Puppet server service if your setup requires it, then confirm that a test node can still fetch its own catalogue.
  5. Review which secrets appear in your catalogues and rotate any that you consider exposed to untrusted or lower-trust clients.
  6. Restrict network access to the Puppet server to the nodes that need it.
  7. Watch the Debian security tracker for the CVE identifier and any further details.

The advisory page also links to neighboring Debian advisories in its previous and next navigation entries: DSA-6608-1 for puppet-agent and DSA-6610-1 for xen. The page we reviewed does not describe their contents or say they are related to this issue, so review them separately on the Debian security announcements list.

Detection and monitoring afterwards

Because the exact trigger is not published, there is no reliable signature to search for. A few sensible habits still help:

  • Review Puppet server logs for catalogue requests where the requesting node name does not match the catalogue requested, if your logging records both.
  • Alert on unexpected new clients or certificate requests on the Puppet server.
  • Track package versions across your fleet so a missed host is easy to find.
  • Check the Debian tracker again in the coming days for a CVE and any updated guidance.

If you also run public websites, keep certificate and DNS monitoring in place for them, for example with Webforta Monitor. That is separate from this issue, which concerns internal configuration management.

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. [SECURITY] [DSA 6609-1] trapperkeeper-authorization-clojure security updatelists.debian.org ·
  • Debian
  • Puppet
  • Trapperkeeper
  • DSA
  • access control