Skip to main content
Report · SecurityWeekAbout CVE-2025-32975Published

Critical Quest KACE Vulnerability Potentially Exploited in Attacks

Source SecurityWeek

0
Compare
Authoritative record:CVE-2025-32975· Critical 10.0

Exploited in the wild · KEV due 4 May 2026 : apply the vendor's fix or mitigations to affected systems now.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
10.0Critical
How severe the flaw is on the 0–10 CVSS scale.
KEV deadline
 US federal agencies must patch by this date; a sensible deadline for everyone else. Other KEV due dates
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

  1. Disclosed: evidence found.

    CVE published 24 Jun 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: evidence found.

    Listed in CISA KEV 300 days after disclosure

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

Timeline

  1. CVE ID reserved

    by MITRE Corporation

    , 70 days before disclosure

  2. CVE published

    on cve.org

    , t = 0

  3. In Threat Radar

    record ingested

    , the same day as disclosure

  4. , 300 days after disclosure

  5. KEV remediation due

    US federal deadline

    , 314 days after disclosure

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CISA KEV (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

AI-suggested

Organizations should immediately conduct a thorough inventory to identify any Quest KACE products in use, especially within the education sector. Until official patches are released, implement network segmentation to isolate KACE management servers from critical systems and sensitive data. Enhance monitoring and logging to detect unusual activity related to KACE services, including unexpected network connections or privilege escalations. Restrict access to KACE management interfaces to trusted administrators and use multi-factor authentication where possible. Apply strict firewall rules to limit inbound and outbound traffic to and from KACE servers. Engage with Quest support channels to obtain any available workarounds or interim fixes. Conduct regular backups of critical data and configuration to enable recovery in case of compromise. Educate IT staff and users about the potential threat and encourage vigilance for phishing or social engineering attempts that could facilitate exploitation. Prepare incident response plans specifically addressing potential exploitation of this vulnerability. Once patches are available, prioritize their deployment following thorough testing.

Description

The vulnerability is tracked as CVE-2025-32975 and it may have been exploited in attacks against the education sector. The post Critical Quest KACE Vulnerability Potentially Exploited in Attacks appeared first on SecurityWeek .

References

Community reviews

Loading reviews…