CVE-2025-32975
Quest KACE Systems Management Appliance (SMA) 13.0.x before 13.0.385, 13.1.x before 13.1.81, 13.2.x before 13.2.183, 14.0.x before 14.0.341 (Patch 5), and 14.1.x before 14.1.101 (Patch 4) contains an authentication bypass vulnerability that allows attackers to impersonate legitimate users without valid credentials. The vulnerability exists in the SSO authentication handling mechanism and can lead to complete administrative takeover.
do firstApply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Can a WAF block it? No. The vulnerability involves bypassing authentication in the web appliance's single sign-on mechanism, which is accessed via HTTP requests. The malicious requests appear normal and do not contain unusual patterns that a firewall could reliably distinguish from legitimate traffic.
Also consider: patch · add auth middleware
Based on an AI reading of the CVE description, and no vendor rule found yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Is CVE-2025-32975 being exploited?
Yes. CVE-2025-32975 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2025-32975?
CVE-2025-32975 is rated Critical with a CVSS score of 10.0. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2025-32975?
Yes. A fix has been recorded for CVE-2025-32975. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2025-32975 affect?
CVE-2025-32975 affects quest:kace_systems_management_appliance. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
cisa ssvc
- exploitation
- active
- automatable
- yes
- technical impact
- total
Assessed by CISA 20 Apr 2026 (SSVC 2.0.3).
timeline
- 24 Jun 2025Published
- 20 Apr 2026Added to CISA KEV (exploited in the wild) · 299 days (about 10 months) later
- 20 Apr 2026CISA SSVC assessment: exploitation active · same day later
- 21 Apr 2026CVE record last updated · 1 day later
- 4 May 2026CISA remediation due date (US federal agencies) · 13 days later
- 2 Nov 2026Analysed by vulneraibility.com · 183 days (about 6 months) later
- Linksupport.quest.com /kb/4379499/quest-response-to-kace-sma-vulnerabilities-cve-2025-32975-cve-2025-3
- Linkseclists.org /fulldisclosure/2025/Jun/22
- Linkseralys.com /research/CVE-2025-32975.txt
- Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-32975
- Linkseclists.org /fulldisclosure/2025/Jun/25
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.