Skip to main content
VulnerabilityPublished Updated

CVE-2024-28213: NAVER nGrinder · Deserialization of Untrusted Data

Affects NAVER nGrinderSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical : upgrade to 3.5.9 as a priority.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.1% chance of exploitation in 30 days – higher than 67% 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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Mar 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 26 Oct 2026.

What to do

Upgrade com.navercorp/ngrinder to 3.5.9.

Affected software

ProductAffectedFixed in
Mavencom.navercorp/ngrinderpkg:maven/com.navercorp/ngrinderOther threatsAffected
  • <3.5.9
Fixed in
  • 3.5.9

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  1. Immediately upgrade all nGrinder instances to version 3.5.9 or later, where the vulnerability is patched.
  2. Restrict network access to nGrinder servers by implementing firewall rules or VPN access to limit exposure to trusted users and systems only.
  3. Employ application-layer filtering or Web Application Firewalls (WAFs) to detect and block suspicious serialized object payloads.
  4. Monitor logs and network traffic for unusual deserialization activity or unexpected Java object payloads.
  5. Conduct regular security assessments and code reviews focusing on deserialization processes in custom extensions or integrations with nGrinder.
  6. Educate development and operations teams about the risks of unsafe deserialization and enforce secure coding practices.
  7. If immediate patching is not feasible, consider disabling or isolating features that accept serialized objects from untrusted sources until updates can be applied.
  8. Maintain an incident response plan to quickly address any signs of compromise related to this vulnerability.

Description

nGrinder before 3.5.9 allows to accept serialized Java objects from unauthenticated users, which could allow remote attacker to execute arbitrary code via unsafe Java objects deserialization.

References

Community reviews

Loading reviews…