CVE
Samsung Update remote code execution via incorrect permissions
Affects Samsung Update (PC Updates section) prior to 3.0.111.0. Fixed in 3.0.111.0.
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 3.0.111.0
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Samsung Update (PC Updates section) prior to version 3.0.111.0
- 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
Incorrect permission assignment for critical resource in Samsung Update prior to version 3.0.111.0 allows local attackers to execute arbitrary code.
Who should check
Anyone running Samsung Update on PCs prior to version 3.0.111.0.
“Samsung Update prior to version 3.0.111.0”
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 Update (PC Updates section) prior to version 3.0.111.0Upgrade to a fixed version: 3.0.111.0.
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-21175 (Incorrect permission assignment for critical resource in Samsung Update prior to version 3.0.111.0 allows local attackers to execute…), 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-21175 (entry last updated 2026-11-17):
Affected:
- Samsung Mobile Samsung Update: fixed in 3.0.111.0
Fixed versions: 3.0.111.0.
Conditions (all must be true for the bug to be hit):
- Samsung Update (PC Updates section) prior to version 3.0.111.0 (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-21175 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-21175 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-21175
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-21175"}.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 Update
fixed in 3.0.111.0
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-21175
Is CVE-2026-21175 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?
Samsung Update has an incorrect permission assignment for a critical resource, which lets a local attacker execute arbitrary code on the machine.Source: security.samsungmobile.com
Which versions are affected by CVE-2026-21175?
Samsung Update: before 3.0.111.0.Source: cve.now feed data
Am I affected, and how do I check?
Samsung Update versions prior to 3.0.111.0 are affected, in the PC Updates section of the product. To check a installed copy, look up its version in the Samsung Update application.Source: security.samsungmobile.com
How do I fix CVE-2026-21175?
Update Samsung Update to version 3.0.111.0 or later, which is the fixed version named in the advisory.Source: security.samsungmobile.com