Skip to main content
VulnerabilityPublished Updated

CVE-2024-28211: 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, 12:54 UTC

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

To mitigate CVE-2024-28211, organizations should immediately upgrade nGrinder to version 3.5.9 or later, where the vulnerability is addressed. If upgrading is not immediately feasible, restrict network access to the nGrinder server, especially blocking inbound connections to JMX/RMI ports from untrusted networks. Implement network segmentation to isolate testing environments from production and sensitive systems. Disable or tightly control JMX/RMI services if they are not required for operational purposes. Employ application-layer firewalls or intrusion detection systems to monitor and block suspicious RMI/JMX traffic. Regularly audit and monitor logs for unusual connection attempts to JMX/RMI services. Educate development and testing teams about the risks of deserialization vulnerabilities and enforce secure coding practices to avoid similar issues in custom extensions or scripts. Finally, maintain an up-to-date inventory of nGrinder deployments to ensure all instances are patched promptly.

Description

nGrinder before 3.5.9 allows connection to malicious JMX/RMI server by default, which could be the cause of executing arbitrary code via RMI registry by remote attacker.

References

Community reviews

Loading reviews…