CVE-2025-0994: Trimble Cityworks Deserialization
Trimble Cityworks · listed in the CISA catalog of actively exploited vulnerabilities since 2025-02-07.
- CVSS v4.0 (CVE record)
- 8.6
- high
- EPSS (exploit probability, 30 days)
- 35%
- higher than 98.4% of all CVEs
- Added to CISA KEV
- 2025-02-07
- US federal due date 2025-02-28
- Automatable (CISA SSVC)
- no
- technical impact: total
CVE-2025-0994 explained
CVE-2025-0994 is a deserialization of untrusted data vulnerability in Trimble Cityworks and Cityworks with office companion. An authenticated user could use it to execute code remotely on the customer's Microsoft Internet Information Services (IIS) web server. CISA lists it as known to be exploited by attackers.
Impact
An attacker with valid credentials can achieve remote code execution on the IIS web server hosting Cityworks. CISA rates the technical impact as total, meaning full control of the affected component. CISA rates it as not automatable, so exploitation requires manual steps rather than mass scanning. Because it is in CISA's Known Exploited Vulnerabilities catalog, attackers are known to use it. Ransomware use is listed as unknown.
Who is affected
The CVE record lists Trimble Cityworks versions before 15.8.9 as affected; the fix is in 15.8.9. Trimble Cityworks (with office companion) versions before 23.10 are affected; the fix is in 23.10. Version data comes from the CVE record as published by its CNA (icscert).
Written with AI from the data on this page and checked against it automatically.
Official description
Trimble Cityworks versions prior to 15.8.9 and Cityworks with office companion versions prior to 23.10 are vulnerable to a deserialization vulnerability. This could allow an authenticated user to perform a remote code execution attack against a customer’s Microsoft Internet Information Services (IIS) web server.
CISA required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
CISA notes
Affected and fixed versions
From the CVE record published by the vendor or CVE numbering authority.
- Trimble CityworksAffectedFixed in
- < 15.8.9
- 15.8.9
- Trimble Cityworks (with office companion)AffectedFixed in
- < 23.10
- 23.10
| Product | Affected | Fixed in |
|---|---|---|
| Trimble Cityworks |
|
|
| Trimble Cityworks (with office companion) |
|
|
How to fix it
- Update to the fixed version for your product:
- Trimble Cityworks: 15.8.9
- Trimble Cityworks (with office companion): 23.10
- Vendor advisory: learn.assetlifecycle.trimble.com/i/1532182-cityworks-cust…
- CISA's deadline for US federal agencies: 2025-02-28 (passed) – a useful benchmark for everyone else, too.
Vendor solution:
- Trimble will be releasing updated versions to both 15.x (15.8.9 available January 28, 2025) and Cityworks 23.x software releases (23.10 available January 29, 2025).
- Information on the updated versions will be available through the normal channels via the [Cityworks Support Portal]( cityworks.my.site.com/)(Login required).
- On-premise customers should install the updated version immediately.
- These updates will be automatically applied to all Cityworks Online (CWOL) deployments.
Workaround:
- Trimble has observed that some on-premise deployments may have overprivileged Internet Information Services (IIS) identity permissions.
- For avoidance of doubt, and in accordance with Trimble's technical documentation, IIS should not be run with local or domain level administrative privileges on any site.
- Please refer to the direction in the latest release notes in the [Cityworks Support Portal]( cityworks.my.site.com/)(Login required) for more information on how to update IIS identity permissions.
- Trimble's CWOL customers have their IIS identity permissions set appropriately and do not need to take this action.
- Trimble has observed that some deployments have inappropriate attachment directory configurations.
- Trimble recommends that attachment directory root configuration should be limited to folders/subfolders which only contain attachments.
- Please refer to the direction in the latest release notes in the [Cityworks Support Portal]( cityworks.my.site.com/)(Login required) for more information on how to ensure proper configuration of the attachment directory.
What to do
- Update Trimble Cityworks to
15.8.9or later. - Update Trimble Cityworks (with office companion) to
23.10or later. - Follow the vendor advisory and apply any additional mitigations Trimble provides.
- Restrict network access to the Cityworks IIS server and review accounts with access to Cityworks.
- Check the IIS servers for signs of compromise, since the vulnerability is known to be exploited.
Written with AI from the data on this page and checked against it automatically.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- No – each attack needs manual steps
- Technical impact
- Total – full control of the component or total information disclosure
Weakness: CWE-502 Deserialization of Untrusted Data
Questions about CVE-2025-0994
- Does an attacker need an account to exploit CVE-2025-0994?
- Yes. The description states that an authenticated user could perform the remote code execution attack. Limiting and reviewing user accounts reduces exposure, but updating is the actual fix.
- Is this vulnerability being exploited?
- Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2025-02-07, with a US federal due date of 2025-02-28. Whether it is used in ransomware campaigns is listed as unknown.
- What does CISA require?
- CISA's required action is to apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable. Fixed versions
15.8.9and23.10are named in the CVE record.
Written with AI from the data on this page and checked against it automatically.
References
Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.