CVE-2026-117778
Summary
by MITRE • 10/28/2026
Rejected reason: Reserved in error; never associated with a vulnerability.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Analysis
by VulDB Data Team • 10/28/2026
The identifier provided has been officially designated as reserved in error and does not correspond to any known security vulnerability or software defect. This status indicates that the Common Vulnerabilities and Exposures (CVE) system, which serves as the standard dictionary for publicly disclosed cybersecurity vulnerabilities, contains an entry that was assigned incorrectly during its initial registration process. Such occurrences typically arise from administrative oversights where a CVE ID is issued without a corresponding technical report, proof of concept, or verified flaw in any specific software product. Consequently, this identifier holds no practical value for vulnerability management systems, threat intelligence platforms, or security information and event management tools because there are no exploit conditions, affected versions, or remediation steps associated with it.
From the perspective of industry standards such as CWE (Common Weakness Enumeration) and MITRE ATT&CK, this entry cannot be mapped to any specific weakness type or attack technique since no underlying technical flaw exists. Security professionals relying on CVE data for risk assessment must treat this identifier as null within their databases to avoid false positives in scanning results or misallocation of remediation resources. The presence of such reserved entries highlights the importance of rigorous validation procedures during the CVE Numbering Authority (CNA) assignment process, ensuring that only verified vulnerabilities receive unique identifiers. Organizations should configure their vulnerability scanners and asset management tools to filter out these non-functional IDs to maintain data integrity and operational efficiency in their security posture assessments.