CVE-2025-27925 json
Nintex Automation 5.6 and 5.7 before 5.8 has insecure deserialization of user input.
published last yr. modified 4mo ago also EUVD-2025-7825
- cvss
- 8.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 35%
- public exploits
- 0
- none known
Summary
Nintex Automation 5.6 and 5.7 before 5.8 has insecure deserialization of user input.
Patch / fix
- Nintex Automation 5.8
Is CVE-2025-27925 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- last yr.
Exploit prediction
0.41% chance of exploitation in the next 30 days, higher than 35% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.5 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H |
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Nintex Automation
Classification
- Weakness
-
- CWE-502 Deserialization of Untrusted Data
References
-
help.nintex.com
/en-US/platform/ReleaseNotes/K2Five.htm
release-notes
Sources
- CVE List CVE-2025-27925
- NVD CVE-2025-27925
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.