CVE
Samsung Device Care local code execution via unquoted search path
Affects Samsung Device Care versions prior to 4.0.80 on Samsung Mobile devices. Fixed in 4.0.80.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
- Exploited
- No known exploitation
- Fix
- Fixed in 4.0.80
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Samsung Device Care versions prior to 4.0.80
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 15/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
Unquoted search path or element in Samsung Device Care prior to version 4.0.80 allows local attackers to execute arbitrary code.
Who should check
Teams managing Samsung PCs running Samsung Device Care older than 4.0.80
“Unquoted search path or element in Samsung Device Care prior to version 4.0.80”
cve.now Index
- Exploitation0/40No signal
- Exposure5/25Specific setups only
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.6/10CVSS 8.6, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 25 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Samsung Device Care versions prior to 4.0.80Upgrade to a fixed version: 4.0.80.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-21176 (Unquoted search path or element in Samsung Device Care prior to version 4.0.80 allows local attackers to execute arbitrary code.), 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-21176 (entry last updated 2026-11-17):
Affected:
- Samsung Mobile Samsung Device Care: fixed in 4.0.80
Fixed versions: 4.0.80.
Conditions (all must be true for the bug to be hit):
- Samsung Device Care versions prior to 4.0.80 (source: https://security.samsungmobile.com/serviceWeb.smsb?year=2026&month=11)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: local access, no login, no user action.
CISA KEV: CVE-2026-21176 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-21176 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://security.samsungmobile.com/serviceWeb.smsb?year=2026&month=11
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-21176
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-21176"}.Timeline
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- CVE published
- First seen by cve.now1 day
- Record last updated
Affected versions
- Samsung Mobile Samsung Device Care
fixed in 4.0.80
Evidence 3
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 1
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-21176
Is CVE-2026-21176 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: cve.now feed data
What does this mean?
The Samsung Device Care service has an unquoted search path or element, a flaw in how the program location is written. A local attacker who can place a crafted file in the right location could get the software to run arbitrary code.Source: security.samsungmobile.com
Which versions are affected by CVE-2026-21176?
Samsung Device Care: before 4.0.80.Source: cve.now feed data
Am I affected, and how do I check?
Samsung Device Care versions prior to 4.0.80 are affected. To check, open the Samsung Device Care app and look at its version number in the app information or settings.Source: security.samsungmobile.com
How do I fix CVE-2026-21176?
Update Samsung Device Care to version 4.0.80 or later, which is the fixed version.Source: security.samsungmobile.com