CVE-2026-117857
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 referenced has been officially designated as reserved due to an administrative or procedural error and does not correspond to any known software flaw, security weakness, or exploitable condition within the Common Vulnerabilities and Exposures ecosystem. This status indicates that while the number was previously allocated or listed in a draft capacity, it lacks the necessary technical evidence, proof of concept, or vendor confirmation required to classify it as an active vulnerability. Consequently, there is no associated CVE database entry detailing specific attack vectors, affected software versions, or remediation steps because the entity never existed as a distinct security issue.
From a threat intelligence perspective, this classification serves as a critical data integrity marker for analysts and automated scanning tools. It prevents false positives in vulnerability management platforms that might otherwise flag systems based on outdated or erroneous identifier mappings. Security operations centers should treat such reserved identifiers with caution during incident response investigations to avoid wasting resources on non-existent threats. The presence of these entries often stems from duplicate submissions, rejected proposals due to insufficient detail, or administrative oversights during the initial allocation phase by a Certified Numbering Authority.
Industry standards such as CWE (Common Weakness Enumeration) and MITRE ATT&CK do not map this identifier because it represents an absence of vulnerability rather than a specific weakness category like improper input validation or privilege escalation. Therefore, no technical narrative regarding exploitation mechanics, impact on confidentiality integrity or availability, or recommended mitigations can be generated for this specific entry. Organizations relying on automated feeds should ensure their systems are configured to filter out reserved or rejected identifiers to maintain accurate risk assessments and avoid alert fatigue caused by phantom vulnerabilities that have been formally disqualified from the CVE program.