Skip to main content
VulnerabilityPublished

CVE-2026-58257: JeromeDevome GRR · Path Traversal

Affects JeromeDevome GRRSource CVE Database V5

0

Not known to be exploited · CVSS 7.2 High : upgrade to 4.5.0 soon.

Data as of 27 Oct 2026, 22:57 UTC

CVSS 3.1 base score
7.2High
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 4.5.0
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 Oct 2026

  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 GRR and jeromedevome/GRR to 4.5.0.

Affected software

ProductAffectedFixed in
JeromeDevomeGRRAffected
  • <4.5.0
Fixed in
  • 4.5.0
GitHubjeromedevome/GRRpkg:github/jeromedevome/GRROther threatsAffected
  • <4.5.0
Fixed in
  • 4.5.0

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

AI-suggested

Upgrade JeromeDevome GRR to version 4.5.0 or later, where this path traversal vulnerability is fixed. No additional mitigation is required if the system is updated to the fixed version.

Description

CVE-2026-58257 is a path traversal vulnerability in JeromeDevome GRR prior to version 4.5.0. The flaw exists in the database restoration feature, which does not properly validate file paths. An administrator user can exploit this to read or delete arbitrary files on the server, potentially disclosing sensitive information or causing denial of service. The risk is higher if the server runs with elevated privileges. This issue is fixed in version 4.5.0.

References

Community reviews

Loading reviews…