CVE-2025-59374
"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.
do firstApply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Can a WAF block it? No. Malicious code was shipped inside the software itself. It runs from within, so a WAF never sees it.
Also consider: SBOM · artifact signing
Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Is CVE-2025-59374 being exploited?
Yes. CVE-2025-59374 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2025-59374?
CVE-2025-59374 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2025-59374?
Yes. A fix has been recorded for CVE-2025-59374. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2025-59374 affect?
CVE-2025-59374 affects asus:live_update. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
- affectedbefore 3.6.6
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
cisa ssvc
- exploitation
- active
- automatable
- yes
- technical impact
- total
Assessed by CISA 18 Dec 2025 (SSVC 2.0.3).
timeline
- 17 Dec 2025Added to CISA KEV (exploited in the wild)
- 17 Dec 2025Published · same day later
- 18 Dec 2025CISA SSVC assessment: exploitation active · 1 day later
- 7 Jan 2026CISA remediation due date (US federal agencies) · 20 days later
- 26 Feb 2026CVE record last updated · 51 days later
- 2 Nov 2026Analysed by vulneraibility.com · 249 days (about 8 months) later
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.