Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.1amended

compliance-trestle Remote Fetching Mechanism has an Arbitrary File Write via Cache Path Traversal

CVE-2026-45725GHSA-g3vg-vx23-3858

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (compliance-trestle 4.0.3, 3.12.2), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
7.1 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2026-45725: 0.47% estimated exploitation activity in the next 30 days; percentile 40.38 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary The compliance-trestle library's remote fetching cache mechanism (HTTPSFetcher and SFTPFetcher) constructs the local cache file path from the URL path component without sanitizing path traversal sequences (../). When a remote OSCAL profile references a URL with traversal in its path, the HTTP response body is written to a location outside the intended cache directory, enabling arbitrary file write with attacker-controlled content to the filesystem. Attack chain: Malicious OSCAL profile → HTTPS fetch → cache path traversal → arbitrary file write → RCE (via cron, SSH keys, etc.) Affected Component Repository: https://github.com/IBM/compliance-trestle File: trestle/core/remote/cache.py (lines 259-266 for HTTPSFetcher, lines 328-333 for SFTPFetcher) Version: v4.0.2 (latest as of 2026-04-30) Vulnerable Code cache.py:259-266 — HTTPSFetcher cache path construction cache.py:285-295 — Content written to traversed path cache.py:328-333 — SFTPFetcher (identical pattern) Root Cause: 1.…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-g3vg-vx23-3858

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-g3vg-vx23-3858

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-45725

Advisory: compliance-trestle Remote Fetching Mechanism has an Arbitrary File Write via Cache Path Traversal
IDs: CVE-2026-45725, GHSA-g3vg-vx23-3858
Record: https://patchnext.com/advisories/cve-2026-45725 (revision 3, source checked 26 Oct 2026, 13:41 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: compliance-trestle 4.0.3, 3.12.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI compliance-trestle: affected >= 4.0.0, <= 4.0.2; < 3.12.2; fixed in 3.12.2, 4.0.3

## Suggested inspection (read-only)
- `python -m pip show compliance-trestle`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on compliance-trestle.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-g3vg-vx23-3858 (OSV record GHSA-g3vg-vx23-3858 lists affected ranges: PyPI compliance-trestle >=4.0.0 =0 <3.12.2 (fixed))
- Verified: https://github.com/advisories/GHSA-g3vg-vx23-3858 (GitHub-reviewed advisory GHSA-g3vg-vx23-3858 lists affected ranges: PyPI compliance-trestle >=4.0.0 =0 <3.12.2)

Commands are suggestions: review each one before running it.

Loading voting…