CVE-2024-28212: NAVER nGrinder · Deserialization of Untrusted Data
Affects NAVER nGrinderSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical : upgrade to 3.5.9 as a priority.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 1.0% chance of exploitation in 30 days – higher than 63% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.5.9
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 7 Mar 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Upgrade org.ngrinder/ngrinder to 3.5.9.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Mavenorg.ngrinder/ngrinderpkg:maven/org.ngrinder/ngrinderOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
1. Upgrade nGrinder to version 3.5.9 or later immediately, as this version includes an updated SnakeYAML library that addresses the unsafe deserialization vulnerability. 2. If immediate upgrade is not possible, restrict network access to nGrinder instances by implementing strict firewall rules and network segmentation to limit exposure to trusted users only. 3. Employ Web Application Firewalls (WAFs) or Intrusion Detection/Prevention Systems (IDS/IPS) with rules targeting YAML deserialization attacks to detect and block malicious payloads. 4. Conduct thorough audits of nGrinder deployments to identify any unauthorized changes or signs of compromise. 5. Monitor logs for unusual activity related to YAML processing or unexpected code execution attempts. 6. Educate development and operations teams about the risks of unsafe deserialization and the importance of using updated libraries. 7. Consider implementing runtime application self-protection (RASP) solutions to detect and prevent exploitation attempts in real time. 8. Maintain an incident response plan tailored to remote code execution scenarios to respond swiftly if exploitation occurs.
Description
nGrinder before 3.5.9 uses old version of SnakeYAML, which could allow remote attacker to execute arbitrary code via unsafe deserialization.