dbcve.org
Quickassist TechnologyApplication · Intel

CVE-2025-27713

HIGH · 7.8 CVSS v3.1 Published 2025-11-11
Fix available
A fix is available. Upgrade to 2.6.0-0018 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Out-of-bounds write for some Intel(R) QAT Windows software before version 2.6.0. within Ring 3: User Applications may allow an escalation of privilege. System software adversary with an authenticated user combined with a high complexity attack may enable escalation of privilege. This result may potentially occur via local access when attack requirements are not present without special internal knowledge and requires no user interaction. The potential vulnerability may impact the confidentiality (high), integrity (high) and availability (high) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (none) and availability (none) impacts.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A privilege escalation vulnerability exists in Intel QAT (QuickAssist Technology) Windows software versions prior to 2.6.0. The flaw is an out-of-bounds write occurring in Ring 3 (user mode) that can be exploited by an authenticated local attacker with high complexity to elevate privileges to potentially system level.

MitigationUpgrade Intel QAT Windows software to version 2.6.0 or later to remediate this vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Quickassist TechnologyApplication
Affected:< 2.6.0-0018

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
High
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Intel QAT software is installed
    Open Windows Control Panel > Programs and Features, or run 'Get-WmiObject Win32_Product' in PowerShell, and look for 'Intel QuickAssist Technology' or 'Intel QAT' in the installed programs list
    Affected if Intel QAT software does not appear in the installed programs list - the system is not affected because the vulnerable software is not present
  2. Identify the installed QAT version
    In Programs and Features, click on the Intel QAT entry to view the version, or check the QAT driver file properties at C:\Windows\System32\drivers\qat*.sys (where * is the specific driver filename) by right-clicking and selecting Properties > Details
    Affected if The displayed version is lower than 2.6.0-0018, or the version cannot be determined and the software is present
  3. Verify the QAT service status
    Open Services (services.msc) and look for 'Intel QAT Service' or 'cpa_qat_service', or run 'Get-Service | Where-Object {$_.Name -like "*qat*"}' in PowerShell
    Affected if The QAT service is running - the vulnerable code path is active; however, note that the vulnerability still requires local authenticated access to exploit regardless of service state
  4. Check for QAT-related processes
    Open Task Manager or run 'Get-Process | Where-Object {$_.ProcessName -like "*qat*"}' in PowerShell to see if any QAT user-mode processes are active
    Affected if QAT user-mode processes are running - the vulnerable Ring 3 component is active, though exploitation still requires authenticated local access with high complexity

A system is affected if Intel QAT Windows software version 2.6.0-0018 or later is NOT installed, regardless of whether the QAT service or processes are currently running, since the vulnerable code exists in any version prior to 2.6.0-0018.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.6.0-0018 or later
Fixed in 2.6.0-0018
Interim mitigation

Upgrade Intel QAT Windows software to version 2.6.0 or later to remediate this vulnerability.

Recommended fix High confidence

Intel Quickassist Technology version 2.6.0-0018 or later

  1. Identify the current installed version of Intel Quickassist Technology on the system
  2. Navigate to Intel's official support page or download center for Quickassist Technology
  3. Download version 2.6.0-0018 or later of the Intel QAT software
  4. Apply the update following Intel's standard installation procedure for QAT software
  5. Reboot the system if required by the update installation
  6. Verify the installed version matches or exceeds 2.6.0-0018

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Quickassist Technology Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-27713 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-27713 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data