Security readout for executives and security teams
Plain-English summary
Prevx 3.0.5.220 reportedly allows an unauthenticated attacker to terminate configured processes through the pxscan.sys driver, causing serious service disruption. The record rates availability impact as high, but the structured affected-product data is incomplete and no vendor fix is identified.
Executive priority
Treat confirmed deployments as a high-priority availability risk, especially where listed processes support security, operations, or revenue. Rapidly establish asset exposure and business criticality, then obtain authoritative remediation guidance. Emergency action is not justified solely by active-exploitation claims because none are supplied.
Technical view
The issue involves unsafe handling of a specific IOCTL by pxscan.sys. Processes named under the driver's Files registry key may be terminated, producing denial of service. The supplied CVSS 3.1 score is 7.5, with low complexity and no privileges or user interaction. The reported network attack vector requires further validation against the driver-focused description.
Likely exposure
Potential exposure is limited to systems running Prevx 3.0.5.220 with the pxscan.sys driver and relevant process entries configured. The bundle provides no CPEs, deployment prevalence, or confirmed additional versions, so organizations should not generalize exposure beyond the named version.
Exploitation context
The supplied record does not indicate CISA KEV inclusion or active exploitation. A public GitHub reference exists, which may increase researcher awareness, but the bundle does not establish real-world attacks, exploit reliability, or remote reachability.
Researcher notes
Evidence quality is limited. The narrative specifically names Prevx 3.0.5.220 and pxscan.sys, while structured vendor, product, version, and CPE fields are unavailable. The network CVSS vector appears potentially inconsistent with a driver IOCTL issue; reachability and prerequisites need independent defensive validation. No patch information is provided.
Mitigation direction
- Identify and prioritize systems running Prevx 3.0.5.220 or loading pxscan.sys.
- Check current vendor or successor guidance for supported upgrades, patches, or compensating controls.
- Restrict untrusted access to affected hosts while remediation guidance is confirmed.
- Consider retiring unsupported installations after operational and compatibility review.
Validation and detection
- Inventory installed Prevx versions and confirm whether pxscan.sys is present and active.
- Review the pxscan service configuration and identify processes listed under its Files registry key.
- Monitor affected endpoints for unexplained termination of protected or business-critical processes.
- Validate whether any remote pathway can reach the driver interface in your environment.
- Confirm remediation through vendor documentation and controlled defensive testing.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-400: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2025-60349 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/djackreuter/CVE-2025-60349CVE reference, mitre
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Uncontrolled Resource Consumption
Uncontrolled Resource Consumption represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.