dbcve.org
Quickassist TechnologyApplication · Intel

CVE-2025-27710

MEDIUM · 5.5 CVSS v3.1 Published 2025-11-11
Fix available
A fix is available. Upgrade to 2.6.0-0018 or later.
See remediation →
57/100
Remediation priority · Elevated
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
Untrusted pointer dereference for some Intel(R) QAT Windows software before version 2.6.0. within Ring 3: User Applications may allow an information disclosure. System software adversary with an authenticated user combined with a low complexity attack may enable data exposure. 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 (none) and availability (none) 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

Untrusted pointer dereference vulnerability in Intel QAT Windows user-mode applications (Ring 3) before version 2.6.0 allows an authenticated local attacker with low complexity to potentially expose sensitive information through improper pointer handling.

MitigationUpgrade Intel QAT Windows software to version 2.6.0 or later to address the untrusted pointer dereference 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
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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. Verify Intel QAT software is installed
    Check for Intel QAT installation directory (typically under Program Files or Program Files (x86)) or look for QAT-related services using 'sc query' command
    Affected if No Intel QAT software found - not affected; if present, continue to version check
  2. Determine installed Intel QAT version
    Locate the QAT driver or application executable (commonly qat_driver or similar) and check its file version property, or run 'qat_util -v' if available
    Affected if Version cannot be determined - treat as potentially affected
  3. Compare version against vulnerable range
    Compare your installed version string to the affected range: versions prior to 2.6.0-0018 are vulnerable
    Affected if Installed version is less than 2.6.0-0018 - environment is affected by this CVE
  4. Confirm QAT user-mode application is in use
    Check if Intel QAT user-mode service or application is running (use 'sc query' or Task Manager)
    Affected if QAT user-mode component is actively running - the untrusted pointer dereference can be exploited; if not running, exploitation risk is lower but software should still be updated

Affected if Intel QAT software version is below 2.6.0-0018 and the QAT user-mode application is installed and running on a Windows system.

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 address the untrusted pointer dereference vulnerability.

Recommended fix Moderate confidence

Intel QuickAssist Technology version 2.6.0-0018 or later

  1. Identify the current installed version of Intel QuickAssist Technology software on the Windows system
  2. Download Intel QuickAssist Technology version 2.6.0-0018 or later from the official Intel website or support channels
  3. Before upgrading, back up any critical data and configuration files related to QAT
  4. Stop any running QAT services or applications
  5. Install the updated QAT software version 2.6.0-0018 or newer
  6. Restart the system or QAT services after installation
  7. 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
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-27710 — 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-27710 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