CVE-2025-23090 Overview
This CVE record has been officially withdrawn and rejected by the CVE Program. CVE-2025-23090 was determined to be a duplicate entry of CVE-2025-23083, and as such, this identifier should no longer be used for tracking or remediation purposes.
Critical Impact
This CVE has been withdrawn. Organizations should reference CVE-2025-23083 instead for vulnerability tracking and remediation guidance.
Affected Products
- No affected products listed (CVE rejected/withdrawn)
Discovery Timeline
- 2025-01-22 - CVE-2025-23090 published to NVD
- 2025-07-18 - CVE record withdrawn and marked as duplicate of CVE-2025-23083
Technical Details for CVE-2025-23090
Vulnerability Analysis
CVE-2025-23090 has been formally rejected and withdrawn from the CVE database. The rejection occurred because this CVE identifier was determined to be a duplicate of CVE-2025-23083. When duplicate CVE entries are discovered, the CVE Program withdraws one of the entries to maintain database integrity and prevent confusion in vulnerability tracking.
Organizations that may have previously tracked CVE-2025-23090 should update their vulnerability management records to reference CVE-2025-23083 instead. All technical details, patches, and remediation guidance associated with this vulnerability issue are maintained under the canonical CVE-2025-23083 entry.
Root Cause
This CVE was rejected due to administrative duplication. The underlying vulnerability, if any, is documented under CVE-2025-23083.
Attack Vector
No attack vector information is available for this withdrawn CVE. Please consult CVE-2025-23083 for relevant technical details.
Detection Methods for CVE-2025-23090
Indicators of Compromise
- No IOCs are associated with this withdrawn CVE
- Any indicators previously linked to CVE-2025-23090 should be re-evaluated under CVE-2025-23083
Detection Strategies
- Update vulnerability scanners to recognize CVE-2025-23090 as withdrawn
- Ensure detection rules reference CVE-2025-23083 for the actual vulnerability
- Review any existing alerts or findings referencing CVE-2025-23090 and remap to CVE-2025-23083
Monitoring Recommendations
- Update vulnerability management databases to reflect the rejected status
- Cross-reference any historical findings for CVE-2025-23090 with CVE-2025-23083
How to Mitigate CVE-2025-23090
Immediate Actions Required
- Redirect all remediation efforts to CVE-2025-23083
- Update vulnerability tracking systems to mark CVE-2025-23090 as withdrawn/rejected
- Review any compliance reports or security assessments that reference this CVE
Patch Information
No patches are associated with CVE-2025-23090 as this CVE has been withdrawn. Organizations should consult CVE-2025-23083 for applicable patch information and remediation guidance.
Workarounds
- No workarounds are required for this withdrawn CVE
- Consult the CVE-2025-23083 advisory for any applicable workarounds related to the actual vulnerability
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.


