Skip to main content
VulnerabilityPublished

CVE-2025-20298: Splunk/UniversalForwarder for Windows · The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.

Affects Splunk/UniversalForwarder for WindowsSource CVE Database V5

0

Not known to be exploited · CVSS 8.0 High.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
8.0High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Jun 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
GitHubsplunk/universalforwarderpkg:github/splunk/universalforwarderOther threatsAffected
  • 9.1 – 9.4
4 affected builds
Fixed in–

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

AI-suggested

European organizations should prioritize upgrading Splunk Universal Forwarder for Windows to versions 9.4.2, 9.3.4, 9.2.6, or 9.1.9 as soon as these patches become available. Until patches are applied, organizations should implement strict local access controls to limit the number of users with local access to machines running the Universal Forwarder. Employing application whitelisting and monitoring file system permissions on the installation directory can help detect unauthorized changes. Additionally, organizations should audit and harden the permissions of the Universal Forwarder installation directory manually, ensuring only administrators and the Splunk service account have read/write access. Monitoring logs for unusual activity related to the Universal Forwarder and conducting regular integrity checks on configuration files can provide early warning of exploitation attempts. Network segmentation to isolate critical Splunk infrastructure and the use of endpoint detection and response (EDR) tools can further reduce risk. Finally, organizations should review and update incident response plans to address potential exploitation scenarios involving log manipulation or disruption.

Description

In Universal Forwarder for Windows versions below 9.4.2, 9.3.4, 9.2.6, and 9.1.9, a new installation of or an upgrade to an affected version can result in incorrect permissions assignment in the Universal Forwarder for Windows Installation directory (by default, C:\Program Files\SplunkUniversalForwarder). This lets non-administrator users on the machine access the directory and all its contents.

References

Community reviews

Loading reviews…