Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-r4vp-3vw6-r2x5

Trestle is vulnerable to arbitrary file write via path traversal in author generate commands (Incomplete fix of CVE-2026-46345)

CVSS 7.7 HighEPSS 0.0022 · 12th percentile

Published by the GitHub Advisory Database at 24 Sept 2026, 19:52 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
compliance-trestlePyPI<3.12.4 || >=4.0.0, <4.1.03.12.4, 4.1.0
Identifiers
GHSA-r4vp-3vw6-r2x5 · CVE-2026-57171 · PYSEC-2026-4030
Weakness (CWE)
CWE-22
Tags
Published
24 Sept 2026
Updated
1 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Trestle (compliance-trestle) versions before 3.12.4 and from 4.0.0 before 4.1.0 are vulnerable to arbitrary file write through path traversal in the author catalog-generate, profile-generate and ssp-generate commands. An attacker who can influence the --output argument, for example through a CI pipeline that derives it from repository data, can write generated files outside the trestle workspace as the process owner, and with --force-overwrite can recursively delete an attacker-chosen directory. Upgrade to version 3.12.4 or 4.1.0.

Written 1 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
7.7 High 3.1 CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0022, the 12th percentile, on 10 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:09 UTC First seen by agentprime
  2. 31 Oct 2026, 14:09 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.