dbcve.org
Quickassist TechnologyApplication · Intel

CVE-2025-24519

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
Buffer overflow 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 low complexity attack may enable data manipulation. 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 (none), integrity (high) 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

Buffer overflow vulnerability in Intel QAT (QuickAssist Technology) Windows software prior to version 2.6.0 within Ring 3 user-mode applications allows an authenticated local attacker to potentially escalate privileges and manipulate data.

MitigationUpgrade Intel QAT software to version 2.6.0 or later to address the buffer overflow 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
None
Integrity
High
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/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. Check if Intel QAT software is installed
    Open Windows Control Panel > Programs and Features, or run 'Get-WmiObject -Class Win32_Product' via PowerShell, and look for any Intel QuickAssist Technology or QAT-related entries
    Affected if Intel QAT software is not listed in installed programs - the system is not affected because the vulnerable software is not present
  2. Identify the installed Intel QAT version
    In Programs and Features, note the version number shown next to Intel QuickAssist Technology entry, or query the registry key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for Intel QAT entries
    Affected if The displayed version is earlier than 2.6.0-0018 - the system is running a vulnerable version
  3. Verify QAT user-mode components are present
    Check for the presence of QAT user-mode driver files in the Intel QAT installation directory (typically under C:\Program Files\Intel\ or C:\Program Files (x86)\Intel\)
    Affected if QAT driver files exist and the version is below 2.6.0-0018 - the vulnerability is present
  4. Check for active QAT-related processes
    Open Task Manager or run 'Get-Process | Where-Object {$_.ProcessName -like "*QAT*"}' in PowerShell to identify running QAT-related user-mode processes
    Affected if QAT processes are running on a version prior to 2.6.0-0018 - the vulnerable code path could potentially be exploited

A user is affected if Intel QuickAssist Technology software is installed with a version number lower than 2.6.0-0018 on their 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 software to version 2.6.0 or later to address the buffer overflow vulnerability.

Recommended fix Moderate confidence

Intel Quickassist Technology version 2.6.0-0018 or later

  1. Identify the currently installed Intel QuickAssist Technology version on the Windows system
  2. Navigate to the Intel Quickassist Technology download page or contact Intel support to obtain version 2.6.0-0018 or later
  3. Download the updated Intel QAT Windows software package for version 2.6.0-0018 or newer
  4. Backup any critical data and configurations related to the current QAT installation
  5. Stop any running QAT services or applications before proceeding with the upgrade
  6. Run the installer for the updated QAT software version 2.6.0-0018 or later
  7. Follow the on-screen installation prompts to complete the upgrade
  8. Restart the system as required by the installation
Caveat Review Intel release notes for version 2.6.0 to check for any API changes, service modifications, or compatibility considerations with existing applications

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

Fix this in Quickassist Technology Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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