CVE-2025-0994
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.
do firstApply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Can a WAF block it? No. The vulnerability requires an authenticated user to send malicious input that triggers deserialization on the IIS web server. The request likely looks like a normal authenticated request, so a WAF cannot reliably distinguish it from legitimate traffic.
Also consider: allow-list classes · patch
Based on an AI reading of the CVE description, and no vendor rule found yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Is CVE-2025-0994 being exploited?
Yes. CVE-2025-0994 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2025-0994?
CVE-2025-0994 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2025-0994?
Yes. A fix has been recorded for CVE-2025-0994. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2025-0994 affect?
CVE-2025-0994 affects trimble:cityworks. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
- affected< 15.8.9
- affected< 23.10
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
public exploits
Unvetted proof-of-concept code on GitHub: 1 GitHub proof of concept
- rxerium/CVE-2025-0994 · 4 ★
Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.
cisa ssvc
- exploitation
- active
- automatable
- no
- technical impact
- total
Assessed by CISA 15 Aug 2025 (SSVC 2.0.3).
timeline
- 6 Feb 2025Published
- 7 Feb 2025Added to CISA KEV (exploited in the wild) · same day later
- 7 Feb 2025First proof-of-concept repository on GitHub (unvetted) · same day later
- 28 Feb 2025CISA remediation due date (US federal agencies) · 21 days later
- 15 Aug 2025CISA SSVC assessment: exploitation active · 169 days (about 6 months) later
- 21 Oct 2025CVE record last updated · 67 days (about 2 months) later
- 2 Nov 2026Analysed by vulneraibility.com · 377 days (about 1 year) later
- Advisorycisa.gov /news-events/ics-advisories/icsa-25-037-04
- Advisorylearn.assetlifecycle.trimble.com /i/1532182-cityworks-customer-communication-2025-02-05-docx/0?
- Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-0994
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- PoC-in-GitHub: GitHub repositories that claim a proof of concept
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.