CVE-2025-0655 Overview
CVE-2025-0655 has been officially rejected by the CVE Program and should not be used. This CVE Record was identified as a duplicate of CVE-2024-55890. All security professionals, researchers, and users should reference CVE-2024-55890 instead of this rejected CVE identifier.
Critical Impact
This CVE ID has been rejected and marked as a duplicate. Do not use CVE-2025-0655 for vulnerability tracking, reporting, or remediation purposes. Reference CVE-2024-55890 for the authoritative vulnerability record.
Affected Products
- Not applicable - CVE rejected as duplicate
- Reference CVE-2024-55890 for affected product information
Discovery Timeline
- 2025-03-20 - CVE-2025-0655 published to NVD
- 2025-04-15 - CVE rejected and marked as duplicate of CVE-2024-55890 - Last updated in NVD database
Technical Details for CVE-2025-0655
Vulnerability Analysis
This CVE record has been rejected by the CVE Numbering Authority (CNA) because it is a duplicate entry. The vulnerability originally described under CVE-2025-0655 is identical to the issue tracked as CVE-2024-55890. CVE rejection occurs when duplicate entries are identified during the CVE assignment process or through community review.
All technical details, severity information, affected products, and remediation guidance have been removed from this CVE record to prevent accidental usage and ensure security teams reference the correct canonical CVE identifier.
Root Cause
The root cause for this CVE rejection is duplicate assignment. The same vulnerability was assigned two different CVE identifiers, and CVE-2024-55890 has been designated as the authoritative record. This can occur due to parallel disclosure processes or timing issues during CVE assignment.
Attack Vector
For attack vector information, exploitation details, and security impact assessment, please reference the canonical vulnerability record: CVE-2024-55890.
Detection Methods for CVE-2025-0655
Indicators of Compromise
- No IOCs are associated with this rejected CVE record
- Reference CVE-2024-55890 for applicable indicators of compromise
- Update any existing rules or signatures that reference CVE-2025-0655 to use CVE-2024-55890
Detection Strategies
- Search vulnerability management databases for references to CVE-2025-0655 and update to CVE-2024-55890
- Audit security tools and SIEM rules for the deprecated CVE identifier
- Verify threat intelligence feeds have been updated to reflect the CVE rejection
Monitoring Recommendations
- Monitor for CVE-2024-55890 instead of this rejected identifier
- Update vulnerability scanning configurations to track the canonical CVE
- Ensure security advisories and reports reference the correct CVE identifier
How to Mitigate CVE-2025-0655
Immediate Actions Required
- Do not implement mitigations based on CVE-2025-0655 - this CVE has been rejected
- Reference CVE-2024-55890 for authoritative mitigation guidance
- Update vulnerability tracking systems to remove or archive CVE-2025-0655
- Review any security reports or documentation that may reference this deprecated CVE
Patch Information
No patch information is available for this rejected CVE. For patching guidance and vendor security advisories, please consult the canonical vulnerability record CVE-2024-55890.
Workarounds
- Replace all references to CVE-2025-0655 with CVE-2024-55890 in security documentation
- Update vulnerability management workflows to use the correct CVE identifier
- Consult CVE-2024-55890 for any applicable temporary workarounds or mitigations
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.


