CVE-2026-31370
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedHonor E APP is affected by information leak vulnerability, successful exploitation of this vulnerability may affect service confidentiality.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · low confidenceHonor E APP contains an information leak vulnerability that allows unauthorized disclosure of sensitive data, impacting service confidentiality. The medium severity (CVSS 6.3) suggests the exploit may require some level of access or user interaction, though specific technical details of the flaw are not provided.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Honor E APP installed versionCheck the app version in device settings: Settings > Apps > Honor E APP > Version, or use adb shell dumpsys package com.huawei.honoreapp to retrieve versionInfoAffected if Unable to determine version or version cannot be compared to vendor advisories (no patch available yet)
-
Review app permissions grantedNavigate to Settings > Apps > Honor E APP > Permissions, or run: adb shell dumpsys package com.huawei.honoreapp | grep -i permissionAffected if App has permissions to contacts, storage, location, or other sensitive data beyond what its core function requires
-
Examine app data storage locationsCheck app's private directory: adb shell ls -la /data/data/com.huawei.honoreapp/ and shared storage: /sdcard/Android/data/com.huawei.honoreapp/Affected if Sensitive files (credentials, tokens, personal data) are stored in plain text or with weak protection
-
Inspect network traffic for data exposureConfigure a proxy (e.g., Burp Suite, Charles) and capture traffic while using the app; look for sensitive data sent in cleartext or to unauthorized endpointsAffected if App transmits personal or sensitive data without encryption or to unexpected destinations
-
Check for debug or verbose loggingUse adb logcat -d | grep -i honoreapp to review log output; also check for android:debuggable=true in the app manifestAffected if App outputs sensitive information (user data, tokens, system details) to logs in production builds
User is affected if using Honor E APP and the app has access to sensitive data which could be exposed through storage, network traffic, or logs without proper protection.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply any available vendor patches or updates for Honor E APP once released. Until then, limit the app's access to sensitive data and monitor for unauthorized data exposure.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-31370 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-31370 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data