PatchTheCVECVE-2025-63617: ktg-mes before commit a484f96 (2025-07-03) has a fastjson deserialization vulnerability
CVE-2025-63617 is a medium-severity flaw (CVSS 6.5) affecting ktg-mes. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
ktg-mes before commit a484f96 (2025-07-03) has a fastjson deserialization vulnerability. This is because it uses a vulnerable version of fastjson and deserializes unsafe input data.
Why this priority
- Public exploit reference
- Remotely exploitable, no login, no user action
A fixed release or distro patch exists.
Risk facts
| CVSS score | 6.5 (Medium) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | None |
| EPSS exploit chance | 0.3% (top 77%) |
| CISA exploited list | No |
| Weakness | CWE-502 |
| Published | 2025-11-10 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2025-63617?
ktg-mes: upgrade to 2025-10-08. Exact commands for each OS are on this page.
Is CVE-2025-63617 being exploited?
CVE-2025-63617 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2025-63617 affect?
CVE-2025-63617 affects ktg-mes. Severity is medium (CVSS 6.5). ktg-mes before commit a484f96 (2025-07-03) has a fastjson deserialization vulnerability. This is because it uses a vulnerable version of fastjson and deserializes unsafe input data.
How urgent is CVE-2025-63617?
Priority 39/100. Public exploit reference; Remotely exploitable, no login, no user action