- Exploited
- No known exploitation
- Fix
- Fixed in September 2026
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: September 2026.
- Last modified
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.14% · 3rd percentile
- 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? →
- 0/100 · provisional
- 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
Summary
The NAS message handler in affected software fails to properly validate the length field of incoming NAS messages, which can cause memory corruption. No CVSS vector or advisory details are available, so how an attacker reaches the bug and what they can gain beyond memory corruption are not confirmed.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
In the NAS message handler, improper validation of the length field in NAS message causes memory corruption
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity?/10Unknown. No CVSS score or vendor rating
- No patch0/5No signal
What would change the score
- Would score about 55 if added to CISA KEV
- Would score about 50 if CISA's SSVC rates exploitation active
- Would score about 22 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: September 2026.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Samsung Semiconductor Exynos 850
fixed in September 2026
- Samsung Semiconductor Exynos 2100
fixed in September 2026
- Samsung Semiconductor Exynos 1280
fixed in September 2026
- Samsung Semiconductor Exynos 2200
fixed in September 2026
- Samsung Semiconductor Exynos 1330
fixed in September 2026
- Samsung Semiconductor Exynos 1380
fixed in September 2026
- Samsung Semiconductor Exynos 1480
fixed in September 2026
- Samsung Semiconductor Exynos 2400
fixed in September 2026
Show all 19 packagesShow fewer packages
- Samsung Semiconductor Exynos 1580
fixed in September 2026
- Samsung Semiconductor Exynos 2500
fixed in September 2026
- Samsung Semiconductor Exynos 1680
fixed in September 2026
- Samsung Semiconductor Exynos 9110
fixed in September 2026
- Samsung Semiconductor Exynos W920
fixed in September 2026
- Samsung Semiconductor Exynos W930
fixed in September 2026
- Samsung Semiconductor Exynos W1000
fixed in September 2026
- Samsung Semiconductor Exynos Modem 5123
fixed in September 2026
- Samsung Semiconductor Exynos Modem 5300
fixed in September 2026
- Samsung Semiconductor Exynos Modem 5400
fixed in September 2026
- Samsung Semiconductor Exynos Modem 5410
fixed in September 2026
Evidence 1
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-48173
Is CVE-2026-48173 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
Which versions are affected by CVE-2026-48173?
Exynos 850: before September 2026. Exynos 2100: before September 2026. Exynos 1280: before September 2026. Exynos 2200: before September 2026. Exynos 1330: before September 2026. 14 more packages are listed on the page.Source: cve.now feed data
How do I fix CVE-2026-48173?
Upgrade to a fixed version: September 2026.Source: cve.now feed data