VDB-358421 · CVE-2026-31369 · EUVD-2026-24065

Honor PcManager 1.0.0.2 denial of service

CVSS Meta Temp Score CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.	Current Exploit Price (≈) Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.	CTI Interest Score Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
2.8	$0-$5k	3.75-

Summaryinfo

A vulnerability was found in Honor PcManager 1.0.0.2. It has been rated as problematic. This affects an unknown function. The manipulation leads to denial of service. This vulnerability is documented as CVE-2026-31369. The attack needs to be performed locally. There is not any exploit available.

Detailsinfo

A vulnerability was found in Honor PcManager 1.0.0.2 and classified as problematic. This issue affects an unknown function. The manipulation with an unknown input leads to a denial of service vulnerability. Using CWE to declare the problem leads to CWE-404. The product does not release or incorrectly releases a resource before it is made available for re-use. Impacted is availability. The summary by CVE is:

PcManager is affected by type privilege bypass, successful exploitation of this vulnerability may affect service availability

The advisory is shared at honor.com. The identification of this vulnerability is CVE-2026-31369 since 03/09/2026. The exploitation is known to be difficult. An attack has to be approached locally. Neither technical details nor an exploit are publicly available.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-24065). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

Honor

Name

PcManager

Version

1.0.0.2

CPE 2.3info

🔒

CPE 2.2info

🔒

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 2.8
VulDB Meta Temp Score: 2.8

VulDB Base Score: 2.5
VulDB Temp Score: 2.5
VulDB Vector: 🔒
VulDB Reliability: 🔍

CNA Base Score: 3.2
CNA Vector (Honor): 🔒

CVSSv2info

AV	AC	Au	C	I	A
💳	💳	💳	💳	💳	💳
💳	💳	💳	💳	💳	💳
💳	💳	💳	💳	💳	💳

Vector	Complexity	Authentication	Confidentiality	Integrity	Availability
Unlock	Unlock	Unlock	Unlock	Unlock	Unlock
Unlock	Unlock	Unlock	Unlock	Unlock	Unlock
Unlock	Unlock	Unlock	Unlock	Unlock	Unlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Denial of service
CWE: CWE-404
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: No

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-Day	Unlock	Unlock	Unlock	Unlock
Today	Unlock	Unlock	Unlock	Unlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔒

Timelineinfo

03/09/2026 CVE reserved
04/21/2026 +42 days Advisory disclosed
04/21/2026 +0 days VulDB entry created
04/21/2026 +0 days VulDB entry last update

Sourcesinfo

Advisory: honor.com
Status: Confirmed

CVE: CVE-2026-31369 (🔒)
GCVE (CVE): GCVE-0-2026-31369
GCVE (VulDB): GCVE-100-358421
EUVD: 🔒

Entryinfo

Created: 04/21/2026 09:58
Updated: 04/21/2026 12:53
Changes: 04/21/2026 09:58 (59), 04/21/2026 12:53 (1)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.