How severe is CVE-2025-59374?

No CVSS score has been assigned to CVE-2025-59374 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2025-59374?

Affected package information for CVE-2025-59374 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2025-59374?

No fixed release is recorded for CVE-2025-59374 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.

How do I detect CVE-2025-59374 in my code and dependencies?

Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

How do I mitigate CVE-2025-59374 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2025-59374 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-59374 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2025-59374?

CVE-2025-59374 has an EPSS (Exploit Prediction Scoring System) score of 1.2%, placing it in the 68th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

Is CVE-2025-59374 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2025-59374 (ASUS Live Update Embedded Malicious Code Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2025-12-17. CISA required all US federal civilian agencies to remediate this vulnerability by 2026-01-07. The required action was: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2025-59374?

CVE-2025-59374 is classified as CWE-506 (CWE-506). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2025-59374 published, and has it been updated?

CVE-2025-59374 was published on December 17, 2025 and was last updated on February 26, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CVE-2025-59374: exploited in the wild

Exploitation Status

Actively exploited in the wild

Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2025-12-17. Federal agencies were required to remediate by 2026-01-07.
CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2025-59374.

EPSS Exploitation Probability

via FIRST.org ↗

1.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs68th percentile — riskier than 68% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Description

"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.

Affected Products

1 product · 1 configurations

Application

live updateasus

< 3.6.8

range

Detection & mitigation playbook

Vulnerability

Detect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Remediation status
No fixed release is recorded for CVE-2025-59374 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

"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.

O3 Security · Impact-Aware SCA

Is CVE-2025-59374 in your dependencies?

Find it across , including transitive dependencies.

Scan my dependencies How O3 SCA works

CVE-2025-59374