Skip to main content
VulnerabilityPublished

CVE-2025-61304: CVE-2025-61304 · OS Command Injection

Affects CVE-2025-61304Source CVE Database V5

0

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

Data as of 26 Oct 2026, 13:47 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.9% chance of exploitation in 30 days – higher than 79% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.017
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 5 Nov 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

Upgrade pentastic-be/CVE-2025-61304 to 1.017.

Affected software

ProductAffectedFixed in
GitHubpentastic-be/CVE-2025-61304pkg:github/pentastic-be/CVE-2025-61304Other threatsAffected
  • <1.017
Fixed in
  • 1.017

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

AI-suggested

  1. Immediately inventory all Dynatrace ActiveGate instances and identify versions up to 1.016 using the vulnerable ping extension.
  2. Isolate vulnerable ActiveGate instances from untrusted networks to limit exposure until patches or official mitigations are available.
  3. Monitor network traffic for anomalous or suspicious requests targeting the ping extension, especially those containing unusual IP address formats or command injection patterns.
  4. Apply strict input validation and filtering at network boundaries or via web application firewalls to block malformed IP address inputs targeting the ping extension.
  5. Engage with Dynatrace support and subscribe to official advisories for timely patch releases or workarounds.
  6. Consider temporarily disabling or restricting the ping extension functionality if feasible without disrupting critical monitoring operations.
  7. Implement robust logging and alerting on ActiveGate components to detect potential exploitation attempts.
  8. Conduct internal penetration testing and vulnerability scanning focused on ActiveGate deployments to verify remediation effectiveness.
  9. Educate IT and security teams about the vulnerability specifics and the importance of securing monitoring infrastructure.
  10. Review and strengthen overall network segmentation to prevent lateral movement from compromised monitoring systems.

Description

OS command injection vulnerability in Dynatrace ActiveGate ping extension up to 1.016 via crafted ip address.

References

Community reviews

Loading reviews…