CVE-2025-60038
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA vulnerability has been identified in Rexroth IndraWorks. This flaw allows an attacker to execute arbitrary code on the user's system by parsing a manipulated file containing malicious serialized data. Exploitation requires user interaction, specifically opening a specially crafted file, which then causes the application to deserialize the malicious data, enabling Remote Code Execution (RCE). This can lead to a complete compromise of the system running Rexroth IndraWorks.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceRexoth IndraWorks contains a deserialization vulnerability where parsing a manipulated file with malicious serialized data allows arbitrary code execution. The attacker crafts a specially crafted file that, when opened by a user, causes the application to deserialize the malicious payload, leading to Remote Code Execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 15v24CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed IndraWorks versionCheck the installed software version through Windows Programs and Features, the application Help > About menu, or by locating the installation directory and finding version metadata files. Compare the version number against the affected range: 15v24 and below.Affected if The installed version is 15v24 or any earlier version.
-
Verify file parsing components are presentExamine the IndraWorks installation directory for deserialization-related libraries or components (such as Java deserialization libraries, serialization handlers, or file parsers for proprietary formats). Look for file types commonly associated with IndraWorks projects.Affected if Deserialization libraries or file parsing modules exist in the installation and are accessible to the application.
-
Inspect recent file access logsReview Windows Event Logs (Security, Application) and IndraWorks application logs for entries indicating recent file open operations, especially involving files from external or network locations. Check for deserialization errors or exceptions.Affected if Logs show recent attempts to open or parse files, particularly from untrusted sources.
-
Check for user-executed filesExamine the application's recent files list, temporary directories, or recent document locations for .indraworks, project files, or other proprietary file types that may have been opened recently.Affected if Users have recently opened files that could contain serialized payloads.
A user is affected if Bosch Rexroth IndraWorks version 15v24 or below is installed and the application is used to open files, since the vulnerability is triggered during deserialization of manipulated files.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply vendor-provided patches for Rexoth IndraWorks. Until a patch is available, exercise extreme caution with files from untrusted sources and consider network segmentation to limit exposure.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-60038 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-60038 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data