CVE-2026-5664 Overview
This CVE has been rejected and should not be used. CVE-2026-5664 was identified as a reservation duplicate of CVE-2026-30078. All CVE users should reference CVE-2026-30078 instead of this candidate.
Critical Impact
This CVE entry has been rejected and withdrawn. No vulnerability information is associated with this identifier. Please reference CVE-2026-30078 for the actual vulnerability details.
Affected Products
- No affected products - CVE rejected
Discovery Timeline
- 2026-04-06 - CVE-2026-5664 published to NVD as rejected
- 2026-04-06 - Last updated in NVD database
Technical Details for CVE-2026-5664
Vulnerability Analysis
This CVE candidate has been officially rejected by the CVE Numbering Authority. The rejection reason states that CVE-2026-5664 is a reservation duplicate of CVE-2026-30078. This means the same vulnerability was accidentally assigned two different CVE identifiers during the reservation process, and CVE-2026-30078 has been designated as the authoritative identifier.
All technical details, references, and descriptions have been intentionally removed from this CVE entry to prevent accidental usage by security researchers, vulnerability scanners, and security teams.
Root Cause
This is not a software vulnerability but rather an administrative CVE assignment error. The root cause is a duplicate reservation in the CVE assignment process where the same vulnerability received two different candidate numbers.
Attack Vector
Not applicable - this CVE has been rejected. For vulnerability and attack vector information, please refer to CVE-2026-30078.
Detection Methods for CVE-2026-5664
Indicators of Compromise
- Not applicable - this CVE has been rejected and contains no vulnerability data
- Any security tools flagging CVE-2026-5664 should be updated to reference CVE-2026-30078
Detection Strategies
- Update vulnerability scanners and security tools to ignore CVE-2026-5664
- Configure scanning tools to use CVE-2026-30078 for the associated vulnerability
- Review any historical alerts or reports referencing this CVE and update to the correct identifier
Monitoring Recommendations
- No active monitoring required for this rejected CVE
- Ensure security information feeds are updated to properly handle rejected CVE entries
How to Mitigate CVE-2026-5664
Immediate Actions Required
- Reference CVE-2026-30078 for all vulnerability management activities
- Update any internal documentation or tracking systems that reference CVE-2026-5664
- Ignore any security scanner findings that reference this rejected CVE identifier
Patch Information
No patch information is available for this rejected CVE. Please consult CVE-2026-30078 for relevant patching guidance and remediation steps.
Workarounds
- No workarounds required - this CVE has been rejected
- Redirect all vulnerability management efforts to CVE-2026-30078
- Update vulnerability databases and internal tracking systems to reflect the correct CVE identifier
# No configuration required - CVE rejected
# Reference CVE-2026-30078 for applicable mitigations
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.


