# CVE-2025-59339: The Bastion ttyrec files are not signed after encryption by the osh-encrypt-rsync script

> The osh-encrypt-rsync script fails to sign encrypted session logs, allowing attackers to tamper with audit trails without detection.

- **Severity:** Medium 4.4 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Sep 2025
- **Updated:** 17 Sep 2025
- **Also known as:** GHSA-h66q-g57p-rgg6

## What is CVE-2025-59339?

CVE-2025-59339 is a medium-severity vulnerability in ovh the-bastion, published on 17 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Bastion provides authentication, authorization, traceability and auditability for SSH accesses. Session-recording ttyrec files, may be handled by the provided osh-encrypt-rsync script that is a helper to rotate, encrypt, sign, copy, and optionally move them to a remote storage periodically, if configured to. When running, the script properly rotates and encrypts the files using the provided GPG key(s), but silently fails to sign them, even if asked to.

Weakness: CWE-325 (Missing Cryptographic Step)

## Which versions are affected by CVE-2025-59339?


## How do I fix CVE-2025-59339?

No fix has been published for CVE-2025-59339 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-59339 being exploited?

There is no known exploitation of CVE-2025-59339 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-59339 and fix it if it is affected.

What it is: CVE-2025-59339 is a medium-severity vulnerability in ovh the-bastion, published on 17 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-59339 in the wild and no public exploit code.

Affected product: ovh the-bastion. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-59339/ (Markdown: https://insights.sbomify.com/CVE-2025-59339/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-59339
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-59339
- OSV: https://osv.dev/vulnerability/CVE-2025-59339

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-59339/
Summaries are generated and may contain mistakes; the official description above is the record.