CVE-2025-59339VulnerabilityPublished 17 Sep 2025

CVE-2025-59339: ovh the-bastion · Missing Cryptographic Step

Affects ovh the-bastionSource CVE Database V5

Not known to be exploited · CVSS 4.4 Medium : upgrade to 3.22.00 when convenient.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

4.4Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 0% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 3.22.00

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N

Attack Vector: Local
Attack Complexity: Low
Privileges Required: High
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 17 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade ovh the-bastion to 3.22.00.

Affected software

Product	Affected	Fixed in
ovh the-bastion	Affected <3.22.00	Fixed in 3.22.00

AI-suggested

1. Upgrade the-bastion to version 3.22.00 or later once available, where the signing functionality in osh-encrypt-rsync is correctly implemented. 2. If you cannot patch yet, implement compensating controls such as: - Manually verifying the integrity of session recordings using alternative cryptographic methods or external tools. - Restricting access to the session recording files and the osh-encrypt-rsync script to trusted administrators only. - Enhancing monitoring and alerting around SSH access and session recording processes to detect suspicious activity. 3. Review and harden the configuration of the-bastion, ensuring that encryption and signing options are correctly set and tested. 4. Consider integrating additional logging and audit mechanisms that provide independent verification of session integrity. 5. Conduct regular audits of session recording files to detect any unauthorized modifications. 6. Educate security teams about the limitations of current session recording integrity until the vulnerability is fixed.

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.

Impact

For European organizations, this vulnerability undermines the trustworthiness of SSH session audit logs managed by the-bastion. Many regulated industries in Europe, such as finance, healthcare, and critical infrastructure, rely heavily on accurate and tamper-proof audit trails for compliance with GDPR, NIS Directive, and other cybersecurity regulations. The inability to cryptographically verify the integrity of session recordings could lead to undetected malicious activity or insider threats, complicating incident response and forensic investigations. This could result in regulatory penalties, reputational damage, and increased risk of persistent unauthorized access. While the vulnerability does not directly expose sensitive data or cause service outages, the loss of audit integrity weakens overall security posture and could be exploited in targeted attacks where attackers aim to erase or alter traces of their activity. Organizations using the-bastion for SSH access control and session recording must be aware that their audit logs may not be fully reliable until the vulnerability is remediated.

CWE-325Missing Cryptographic Step (opens in a new tab)
Base weaknessOWASP Top 10 A04:2025: Cryptographic Failures (opens in a new tab)
The product does not implement a required step in a cryptographic algorithm, resulting in weaker encryption than advertised by the algorithm.
OWASP Cheat Sheets
Cryptographic Storage (opens in a new tab)
Key Management (opens in a new tab)
Transport Layer Protection (opens in a new tab)
User Privacy Protection (opens in a new tab)
Password Storage (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.7 (opens in a new tab)
V2.9.3 (opens in a new tab)
V6.2.2 (opens in a new tab)
Attack patterns
Subvert Code-signing Facilities (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 17 Sep 2025, 18:20 UTC

WeaknessesCWE-325

Technical details

References

Community reviews

Related threats