CVE-2026-117847
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 in the query 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 any vendor's product ecosystem. In the context of global cybersecurity infrastructure managed by organizations such as the MITRE Corporation under the CVE Program, identifiers are assigned only after a vulnerability has been validated, documented, and verified against established criteria for public disclosure. A reserved status indicates that this specific string was either allocated prematurely, duplicated during processing, or marked to prevent confusion with other existing entries without implying any underlying technical defect exists in software systems.
Consequently, there is no associated Common Weakness Enumeration (CWE) classification, nor is there a corresponding entry within the MITRE ATT&CK framework for this specific identifier. Security professionals and automated scanning tools should disregard this reference when conducting vulnerability assessments or threat intelligence analysis because it carries no technical payload, exploit code, or remediation guidance. The presence of such reserved identifiers in logs or databases typically stems from data ingestion errors where non-vulnerability strings were mistakenly processed as potential CVEs rather than actual security advisories.
Organizations encountering this status should verify the integrity of their vulnerability management feeds and ensure that parsing logic correctly filters out reserved or invalid entries to maintain accurate risk scoring. Since no technical flaw is associated with this identifier, there are no specific mitigations, patches, or configuration changes required for systems potentially linked to it. The appropriate action is simply to exclude this entry from security reports and audit trails to prevent false positives in compliance reporting and incident response workflows.