CVE-2025-60037
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 confidenceA deserialization vulnerability in Rexroth IndraWorks allows RCE via a specially crafted file containing malicious serialized data. When a user opens the manipulated file, the application deserializes the malicious payload, executing arbitrary code and achieving full system compromise.
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 versionOpen Windows Control Panel > Programs and Features, or check the installation directory (typically C:\Program Files\Bosch Rexroth\IndraWorks) for version information. You can also check the Windows Registry under HKEY_LOCAL_MACHINE\SOFTWARE\BoschRexroth\IndraWorks for the installed version value.Affected if The displayed version is 15v24 or any earlier version (e.g., 15v23, 14v30, etc.)
-
Verify the application executable versionLocate the main IndraWorks executable (commonly named IndraWorks.exe or similar launcher) in the installation directory. Right-click the file, select Properties, and examine the File Version and Product Version fields on the Details tab.Affected if The file version shows 15.24.x or lower, indicating an affected release.
-
Determine exposure to untrusted filesCheck if IndraWorks is installed on systems where users have the ability to open files from untrusted sources such as email attachments, removable USB drives, network shares accessible by untrusted users, or downloads from the internet.Affected if Users on the system can open or import files from untrusted or unknown sources directly into IndraWorks without prior sanitization or scanning.
-
Assess application whitelisting statusReview whether application whitelisting (e.g., Windows AppLocker, Windows Defender Application Control) is enabled and configured to block execution of unauthorized binaries or scripts that could be invoked through the deserialization flaw.Affected if No application whitelisting or file-type restrictions are enforced, and the system relies solely on user vigilance to avoid opening malicious files.
A system is affected if IndraWorks version 15v24 or earlier is installed and users can open untrusted crafted files, since the deserialization vulnerability is inherent to the application code in those versions.
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-supplied patches for IndraWorks when available; until then, restrict user ability to open untrusted files, implement application whitelisting, and train users to avoid opening files from untrusted sources.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-60037 — 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-60037 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