CISA ADP Vulnrichment

Why this deserves its current priority

CVSS is 5.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Affected scope and exposure questions

The current feed maps Huawei/EMUI (generic), Huawei/HarmonyOS (generic). Check affected ranges and fixed versions before updating.

Recommended response

1. 1Check inventory. Check lockfiles and deployed manifests for Huawei/EMUI, Huawei/HarmonyOS.
2. 2Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

1. Published upstream

   Aug 17, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

2. Source modified

   Aug 28, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

3. First seen by HOL

   Aug 17, 2026

Sources and claim methodology

• Source referenceconsumer.huawei.com
• Source referenceconsumer.huawei.com

Related CVEs

• Klever-Go: Marketplace settlement mints KLV when referral % + royalty % exceed the bid (negative seller share silently skipped)Same generic ecosystem
• Klever-Go: Integer overflow in split-royalty validation enables unbounded minting of KLV (native token)Same generic ecosystem
• Vikunja: Project duplication bypasses write-permission check on the target parent projectSame generic ecosystem
• dd-trace-rs: Unbounded W3C tracestate parsing may lead to DoSSame generic ecosystem
• Vikunja incomplete fix for CVE-2026-35595: Write-only user can detach shared project from parent hierarchy via parent_project_id=0Same generic ecosystem
• Vikunja: Improper Authorization and Authorization Bypass Through User-Controlled Key in code.vikunja.io/apiSame generic ecosystem