No CVE referenced at NVD for H&M on Android. Absence of CVEs is not a guarantee of security.
- Known vulnerabilities
- 0
- Still open
- 0
- KEV open
- 0
- Max CVSS (open)
- -
Known vulnerabilities (CVE)
No CVE is currently referenced in NVD for this app on its platform.
The absence of CVEs is not a security guarantee : it can also mean nobody has audited or published findings.
Cumulative exposure
Low
Aggregates open CVEs (40%) + KEV (30%) + critical shared permissions (15%) + trackers (10%) + OS EOL (5%). Higher score = more exposed.
-
Open CVEs +0/+50
0 open CVEs, max CVSS 0.0, EPSS 0%
-
Active KEVs +0/+35
0 CISA KEVs still open
-
Permissions +0/+10
0 critical shared permission(s)
-
Trackers +0/+8
0 identification/profiling tracker(s)
-
EOL OS +0/+5
Installed OS is end-of-life
Based on permissions only: no CVE data referenced for this app.
Context
Context
Description
H&M app - shopping made easier! Browse,shop and keep an eye on the latest trends
Data collected and shared
Source: Play Store Data Safety · 17 data item(s) declared
Indicative classification based on data sensitivity. "Shared" = transmitted to third parties (publisher-declared).
Technical details
- Publisher
- H&M
- Distribution channel
- Google Play
- Identifier
- com.hm.goe
FAQ
FAQ: H&M
Why are no CVEs listed for H&M?
No CVE is currently referenced in NVD for H&M (com.hm.goe) with a Android CPE configuration. Either none has been publicly disclosed, or none has been mapped yet. Absence of a CVE is not a security guarantee.
What is the latest known version of H&M?
The most recent version of H&M (com.hm.goe) tracked by Appaloosa Scout is 26.34.0, published by H&M.