Skip to main content
Stopping PHP2SHELL: How SentinelOne Protects Customers From This Attack TechniqueRead More
Vulnerability Database/CVE-2025-4920

CVE-2025-4920: Rejected Duplicate Vulnerability Entry

CVE-2025-4920 is a rejected CVE entry marked as a duplicate of CVE-2025-4918. This occurs when the same vulnerability is assigned multiple identifiers. This article explains rejected CVE entries and guides you to the correct record.

Updated:

CVE-2025-4920 Overview

CVE-2025-4920 has been rejected by the CVE Numbering Authority (CNA) as it is a duplicate of CVE-2025-4918. This CVE identifier is no longer valid and should not be used for vulnerability tracking, remediation, or security assessments.

Critical Notice

This CVE has been rejected and marked as a duplicate. Organizations should reference CVE-2025-4918 for the actual vulnerability details and remediation guidance.

Affected Products

  • No affected products listed (CVE rejected)

Discovery Timeline

  • 2025-05-17 - CVE-2025-4920 published to NVD
  • 2025-05-18 - CVE rejected and marked as duplicate of CVE-2025-4918

Technical Details for CVE-2025-4920

Vulnerability Analysis

This CVE entry has been rejected by the issuing CNA (CVE Numbering Authority). The rejection reason indicates that CVE-2025-4920 is a duplicate of CVE-2025-4918, meaning both CVE identifiers were assigned to the same underlying vulnerability.

When duplicate CVEs are identified, one is typically rejected to prevent confusion in vulnerability tracking and to ensure organizations are not inadvertently tracking the same issue under multiple identifiers. Security teams should consolidate any references to CVE-2025-4920 and instead use CVE-2025-4918 for tracking, patching, and remediation purposes.

Root Cause

Not applicable - this CVE has been rejected as a duplicate entry. The actual root cause analysis for the underlying vulnerability should be referenced under CVE-2025-4918.

Attack Vector

Not applicable - refer to CVE-2025-4918 for attack vector information related to the actual vulnerability.

Detection Methods for CVE-2025-4920

Indicators of Compromise

  • This CVE has been rejected; no specific IOCs apply to this identifier
  • Organizations should reference CVE-2025-4918 for relevant indicators of compromise

Detection Strategies

  • Update any existing detection rules referencing CVE-2025-4920 to use CVE-2025-4918
  • Review vulnerability scanning tools to ensure they correctly handle rejected CVE status
  • Consolidate duplicate findings in security dashboards

Monitoring Recommendations

  • Update vulnerability management databases to reflect the rejected status
  • Ensure security tools fetch the latest CVE status from NVD
  • Monitor CVE-2025-4918 for updates regarding the actual vulnerability

How to Mitigate CVE-2025-4920

Immediate Actions Required

  • Redirect all remediation efforts to CVE-2025-4918
  • Update internal vulnerability tracking systems to reflect the rejected status
  • Remove CVE-2025-4920 from active vulnerability lists and dashboards

Patch Information

No patch information is available for this CVE as it has been rejected. Organizations should consult CVE-2025-4918 for applicable patch and remediation guidance related to the actual vulnerability.

Workarounds

  • No workarounds are applicable for this rejected CVE
  • Reference CVE-2025-4918 for any applicable workarounds or mitigations

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.

Try SentinelOne