Skip to main content
VulnerabilityPublished Updated

CVE-2025-45872: zrlog · Server-Side Request Forgery (SSRF)

Affects zrlogSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 11:42 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 41% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
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 1 Jul 2025

  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

Affected software

ProductAffectedFixed in
GitHubdengxmenglihua/zrlogpkg:github/dengxmenglihua/zrlogOther threatsAffected
  • =3.1.5
Fixed in–

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

AI-suggested

Immediate mitigation steps include restricting outbound HTTP requests from the zrlog server to only trusted destinations via network-level controls such as firewall rules or proxy configurations. Implementing strict input validation and sanitization on the 'downloadUrl' parameter is essential to prevent malicious URLs from being processed. Organizations should monitor web server logs for unusual or unexpected outbound requests originating from the application. Deploying Web Application Firewalls (WAFs) with custom rules to detect and block SSRF patterns can provide additional protection. Until an official patch is available, consider isolating the zrlog server within a segmented network zone with minimal access to internal resources. Regularly update and audit all third-party components and monitor threat intelligence feeds for any emerging exploit code related to this vulnerability. Finally, prepare incident response plans to quickly address any detected exploitation attempts.

Description

zrlog v3.1.5 was discovered to contain a Server-Side Request Forgery (SSRF) via the downloadUrl parameter.

References

Community reviews

Loading reviews…