VulnerabilityPublished 14 Aug 2025

CVE-2025-48862: Bosch Rexroth ctrlX OS – Setup · Use of Unmaintained Third Party Components

Affects Bosch Rexroth ctrlX OS – SetupSource CVE Database V5

Not known to be exploited · CVSS 7.1 High.

Data as of 26 Oct 2026, 15:59 UTC

CVSS 3.1 base score

7.1High

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

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

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

Attack Vector: Local
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Changed
Confidentiality: High
Integrity: None
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: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within 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 14 Aug 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 26 Oct 2026.

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 or the CVSS exploit maturity 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.

cwe-311

What to do

Affected software

Product	Affected	Fixed in
Bosch Rexroth AG ctrlX OS - Setup	Affected =1.20.0 =2.6.0 =3.6.0	Fixed in–

AI-suggested

To mitigate this vulnerability, European organizations should: 1) Immediately review and audit backup procedures for ctrlX OS setups to verify the actual encryption status of backup files rather than relying on interface indications. 2) Implement additional encryption measures for backup files at rest and in transit, such as using full-disk encryption or secure file containers, to ensure confidentiality beyond the built-in mechanisms. 3) Restrict access to backup files strictly to authorized personnel and systems, employing strong access controls and monitoring for unauthorized access attempts. 4) Apply network segmentation and isolate industrial control systems to limit local access vectors that could be exploited. 5) Engage with Bosch Rexroth AG for patches or updates addressing this issue and plan for timely deployment once available. 6) Educate users and administrators about the misleading interface wording to prevent complacency regarding backup security. 7) Conduct regular security assessments and penetration testing focused on backup and key management processes within ctrlX OS environments. These steps go beyond generic advice by focusing on compensating controls and operational changes to address the specific nature of the vulnerability until a vendor patch is released.

Description

Ambiguous wording in the web interface of the ctrlX OS setup mechanism could lead the user to believe that the backup file is encrypted when a password is set. However, only the private key - if available in the backup - is encrypted, while the backup file itself remains unencrypted.

Impact

For European organizations using Bosch Rexroth AG's ctrlX OS, particularly in industrial automation sectors such as manufacturing, automotive, and critical infrastructure, this vulnerability poses a substantial confidentiality risk. Backup files that are assumed to be encrypted may be stored insecurely or transmitted over networks, exposing sensitive configuration data and private keys to attackers with local access or through compromised internal systems. This could facilitate unauthorized system access, intellectual property theft, or sabotage of industrial processes. Given the critical role of industrial control systems in European manufacturing and infrastructure, exploitation could disrupt operations, cause financial losses, and impact supply chains. The scope change indicated by the CVSS vector suggests that exploitation could affect components beyond the initial vulnerable setup interface, potentially compromising broader system security. The lack of integrity and availability impact reduces the risk of direct system manipulation or downtime but does not mitigate the serious confidentiality breach. The absence of known exploits in the wild currently limits immediate risk but does not preclude future targeted attacks, especially as threat actors increasingly focus on industrial control systems in Europe.

CWE-1104Use of Unmaintained Third Party Components (opens in a new tab)
Base weaknessOWASP Top 10 A03:2025: Software Supply Chain Failures (opens in a new tab)
The product relies on third-party components that are not actively supported or maintained by the original developer or a trusted proxy for the original developer.
OWASP Cheat Sheets
OWASP Cheat Sheet Series: Dependency Graph SBOM (opens in a new tab)
OWASP Cheat Sheet Series: Vulnerable Dependency Management (opens in a new tab)
OWASP ASVS 4.0.3
V1.14.3 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

psirt.bosch.com/security-advisories/BOSCH-SA-129652.html (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 14 Aug 2025, 09:33 UTC

WeaknessesCWE-1104

Technical details

References

Community reviews

Related threats