Skip to main content
OneCon26: Gain the advantage in the AI era. Oct. 20–22 in Las Vegas.Register Now
Vulnerability Database/CVE-2025-34085

CVE-2025-34085: Rejected Duplicate CVE Entry Vulnerability

CVE-2025-34085 has been rejected by its CVE Numbering Authority as a duplicate of CVE-2020-36847. This article explains the rejection reason, duplicate status, and provides reference to the original CVE entry.

Updated:

CVE-2025-34085 Overview

CVE-2025-34085 has been rejected and withdrawn by its CVE Numbering Authority (CNA). This CVE identifier was determined to be a duplicate of CVE-2020-36847 and is no longer valid for vulnerability tracking purposes.

Critical Impact

This CVE has been rejected. Organizations should reference CVE-2020-36847 instead for vulnerability tracking and remediation guidance.

Affected Products

  • No products are affected under this CVE ID
  • Please refer to CVE-2020-36847 for affected product information

Discovery Timeline

  • 2025-07-09 - CVE-2025-34085 published to NVD
  • 2025-07-16 - CVE rejected and marked as duplicate of CVE-2020-36847; last updated in NVD database

Technical Details for CVE-2025-34085

Vulnerability Analysis

This CVE entry has been rejected by its CVE Numbering Authority. The rejection indicates that this identifier was erroneously assigned and duplicates an existing CVE entry (CVE-2020-36847). No unique vulnerability exists under this CVE identifier.

Organizations that may have catalogued CVE-2025-34085 in their vulnerability management systems should update their records to reference CVE-2020-36847 instead for accurate tracking and remediation.

Root Cause

Not applicable - this CVE has been rejected as a duplicate entry. The underlying vulnerability, if any, should be researched under CVE-2020-36847.

Attack Vector

Not applicable - this CVE identifier has been withdrawn. Any technical details regarding attack vectors should be obtained from the original CVE-2020-36847.

Detection Methods for CVE-2025-34085

Indicators of Compromise

  • No specific IOCs are associated with this rejected CVE
  • Security teams should reference CVE-2020-36847 for any relevant indicators

Detection Strategies

  • Update vulnerability scanners to ignore CVE-2025-34085 as it is a rejected duplicate
  • Configure detection rules to reference CVE-2020-36847 instead
  • Review existing alerts for CVE-2025-34085 and remap them to the original CVE

Monitoring Recommendations

  • No active monitoring required for this rejected CVE
  • Ensure vulnerability management platforms are updated to reflect the rejected status
  • Consult CVE-2020-36847 for appropriate monitoring guidance

How to Mitigate CVE-2025-34085

Immediate Actions Required

  • Remove CVE-2025-34085 from active vulnerability tracking lists
  • Update vulnerability databases and scanning tools to reflect the rejected status
  • Reference CVE-2020-36847 for any required remediation actions

Patch Information

No patches are associated with CVE-2025-34085 as this CVE has been rejected. Organizations should consult CVE-2020-36847 for patch information related to the underlying vulnerability.

Workarounds

  • No workarounds are necessary for this rejected CVE
  • Redirect all mitigation efforts to CVE-2020-36847
  • Update any documentation or reports referencing CVE-2025-34085 to note its rejected status

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