CVE-2026-72746: Rejected CVE Entry (Duplicate) Overview

CVE-2026-72746 Overview

CVE-2026-72746 has been rejected by its CVE Numbering Authority (CNA). The identifier is a duplicate of CVE-2026-73241 and carries no independent vulnerability data. Security teams tracking this identifier should redirect all research, detection engineering, and remediation activity to the canonical record at CVE-2026-73241.

No affected products, CVSS score, CWE classification, or exploitation details are associated with this rejected entry. The National Vulnerability Database (NVD) retains the identifier for historical traceability only.

Critical Impact
This CVE contains no actionable vulnerability data. Refer to CVE-2026-73241 for the authoritative advisory, affected products, and mitigation guidance.

Affected Products

Not Available — this CVE identifier has been rejected as a duplicate

Discovery Timeline

2026-08-11 - CVE-2026-72746 published to NVD
2026-08-12 - Entry last modified in NVD database and marked as rejected duplicate of CVE-2026-73241

Technical Details for CVE-2026-72746

Vulnerability Analysis

CVE-2026-72746 does not describe a technical vulnerability. The CNA withdrew the identifier after determining it duplicated an existing record. Duplicate CVE assignments typically occur when multiple parties request identifiers for the same underlying flaw, or when a single CNA issues overlapping IDs during coordinated disclosure.

Because the identifier carries no technical content, there is no root cause to analyze, no attack surface to enumerate, and no proof-of-concept to review. All technical substance resides in the canonical record CVE-2026-73241.

Root Cause

The rejection reflects a CVE program housekeeping action, not a software defect. The CNA consolidated duplicate coverage under CVE-2026-73241 to prevent fragmented tracking across vulnerability databases, ticketing systems, and vendor advisories.

Attack Vector

No attack vector applies to this rejected identifier. Consult CVE-2026-73241 for the authoritative attack vector, exploitability metrics, and prerequisites.

The vulnerability details, exploitation mechanics, and affected component information are documented under the canonical CVE record. See the NVD entry for CVE-2026-73241 for technical specifics.

Detection Methods for CVE-2026-72746

Indicators of Compromise

No indicators of compromise are associated with CVE-2026-72746. Detection engineering should reference CVE-2026-73241 for any IOC data published by the CNA or third-party researchers.

Detection Strategies

Update vulnerability management platforms, SIEM correlation rules, and detection content to reference CVE-2026-73241 instead of the rejected identifier.
Audit ticketing systems and internal advisories to remove or redirect references to CVE-2026-72746, preventing duplicate remediation workstreams.

Monitoring Recommendations

Monitor the NVD and the canonical CVE-2026-73241 record for updates, affected product listings, and patch availability.
Confirm that vulnerability scanners and asset inventory tools deduplicate CVE-2026-72746 findings against CVE-2026-73241 to avoid inflated risk metrics.

How to Mitigate CVE-2026-72746

Immediate Actions Required

Redirect all tracking, reporting, and remediation activity from CVE-2026-72746 to CVE-2026-73241.
Close any open tickets or risk register entries tied to CVE-2026-72746 with a reference to the canonical identifier.
Notify downstream consumers of vulnerability data, including managed service providers and audit teams, of the deduplication.

Patch Information

No patch is associated with CVE-2026-72746. Patch availability, vendor advisories, and remediation timelines are published under CVE-2026-73241. Review that record for vendor-supplied fixes and configuration guidance.

Workarounds

No workarounds apply to this rejected identifier. Apply any workarounds documented under CVE-2026-73241.
Ensure vulnerability management tooling suppresses duplicate alerts by mapping CVE-2026-72746 to CVE-2026-73241 in local reference data.