dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 7 Jan 2026.
Live UpdateApplication · Asus

CVE-2025-59374

CRITICAL · 9.8 CVSS v3.1 Published 2025-12-17
Fix available
A fix is available. Upgrade to 3.6.8 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild Remotely reachable No privileges 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
"UNSUPPORTED WHEN ASSIGNED" Certain versions of the ASUS Live Update client were distributed with unauthorized modifications introduced through a supply chain compromise. The modified builds could cause devices meeting specific targeting conditions to perform unintended actions. Only devices that met these conditions and installed the compromised versions were affected. The Live Update client has already reached End-of-Support (EOS) in October 2021, and no currently supported devices or products are affected by this issue.

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 · moderate confidence

This is a supply chain compromise where unauthorized modifications were introduced into ASUS Live Update client builds. The compromised builds contained code that would cause devices meeting specific targeting conditions to perform unintended actions, effectively functioning as a backdoor in the update mechanism.

MitigationSince the affected Live Update client reached End-of-Support in October 2021 and no currently supported devices are affected, organizations should identify any legacy ASUS systems that may have used this software and decommission, isolate, or upgrade them to supported solutions.

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
Live UpdateApplication
Affected:< 3.6.8

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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. Check if ASUS Live Update client is installed
    Search for the ASUS Live Update application on the system - look for executables named 'LiveUpdate.exe' or similar in typical ASUS installation directories such as C:\Program Files\ASUS\LiveUpdate or C:\Program Files (x86)\ASUS\LiveUpdate, or check the Windows Programs and Features list
    Affected if The application is found installed on the system
  2. Identify the installed version of ASUS Live Update
    Right-click the Live Update executable or access it via Add/Remove Programs, and locate the version information typically displayed in the program's Properties (Details tab) or in the About/Version dialog within the application
    Affected if The version number displayed is less than 3.6.8 (for example, 3.6.7, 3.6.6, etc.)
  3. Verify the software is the legacy EOS client
    Confirm the installation is the standalone ASUS Live Update client utility (not a component bundled with newer MyASUS or other currently-supported ASUS software)
    Affected if The detected installation is the standalone legacy Live Update utility rather than a current ASUS update mechanism

The system is affected if the legacy standalone ASUS Live Update client is installed and its version is below 3.6.8.

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 3.6.8 or later
Fixed in 3.6.8
Interim mitigation

Since the affected Live Update client reached End-of-Support in October 2021 and no currently supported devices are affected, organizations should identify any legacy ASUS systems that may have used this software and decommission, isolate, or upgrade them to supported solutions.

Recommended fix High confidence
  1. 1. Do not use ASUS Live Update client - it reached End-of-Support (EOS) in October 2021.
  2. 2. If currently running any version of Live Update < 3.6.8, uninstall or disable it immediately.
  3. 3. Migrate to ASUS's current firmware/update mechanisms for supported devices - visit www.asus.com for current supported products.
  4. 4. For devices that only support Live Update and are now EOS, consider replacing with newer hardware that receives active support.
Caveat The Live Update client is End-of-Support and should not be used. No upgrade path exists for EOS software. Migrate to currently supported ASUS products/services.

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

Fix this in Live Update Exploited in the wild — priority engagement
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,290
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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