← Sigma detections
Sigma · CVE exploitation
CVE-2025-60021 exploitation attempt
- severity
- high
- confidence
- 80/100
- generated
- 16 Nov 2026
- Linked CVE
- CVE-2025-60021
Web request carrying the exploit observable of CVE-2025-60021 (EPSS 0.55), taken from the public nuclei template.
False-positive notes
Generated because: EPSS 0.55. Keys on the distinctive part of the exploit request only (path traversal behind a product-specific path, exploit syntax in the query, an unusual parameter); a match on a common path plus a generic token such as ../ or a quote is rejected, never emitted. Needs raw request-URI logging (some web servers normalise ../ away). Scanners hitting the internet produce true-positive ATTEMPTS: correlate with sc-status / response size before declaring compromise.
References
title: Skopnix - CVE-2025-60021 exploitation attemptid: 142481b2-2ef2-5f8e-954b-2c78cdc422ecstatus: experimentaldescription: Web request carrying the exploit observable of CVE-2025-60021 (EPSS 0.55), taken from the public nuclei template.references: - https://skopnix.com/cve/CVE-2025-60021 - https://github.com/projectdiscovery/nuclei-templates/blob/main/http/cves/2025/CVE-2025-60021.yaml - https://nvd.nist.gov/vuln/detail/CVE-2025-60021author: skopnixdate: '2026-11-16'tags: - attack.initial-access - attack.t1190 - cve.2025-60021logsource: category: webserverdetection: selection_1: cs-uri-stem|contains: /pprof/heap cs-uri-query|contains: ${ condition: selection_1falsepositives: - Vulnerability scanners and authorised penetration tests (attempts, not compromise)level: highskopnix-sigma-cve-cve-2025-60021-4e77d3a4.yml
How to deploy on Sigma
- Step 1
- Convert for your SIEM with sigma-cli / pySigma, e.g. sigma convert -t splunk -p sysmon rule.yml.
- Step 2
- Run it as a hunt first: every rule ships as status experimental.
- Step 3
- Promote to an alert once a week of results is clean on your data.
- Check
- The processing pipeline must map the logsource (firewall, dns, proxy, webserver, process_creation) to your field names.