CVE-2025-0994
Trimble Cityworks Deserialization Vulnerability
Trimble Cityworks
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.
Exploitation status
CISA Known Exploited Vulnerabilities
Listed by CISA on 7 February 2025. US federal agencies were required to remediate it by 28 February 2025.
EPSS — exploitation probability
FIRST puts the probability of exploitation activity in the next 30 days at 31.3%, which is higher than 98.3% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Frequently asked questions
Is CVE-2025-0994 being exploited by ransomware groups?
No ransomware group in this database is currently recorded as exploiting CVE-2025-0994.
What does CVE-2025-0994 affect?
CVE-2025-0994 affects Trimble Cityworks. 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.
How severe is CVE-2025-0994?
CVE-2025-0994 is rated HIGH with a CVSS base score of 8.8. EPSS puts the probability of exploitation in the next 30 days at 31.3%, higher than 98.3% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 28 February 2025.
How should organisations respond to CVE-2025-0994?
Apply the vendor patch for Trimble Cityworks as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.