CVE-2026-87122 Overview
CVE-2026-87122 is a rejected CVE identifier. The MITRE CVE Program marked this entry as a reservation duplicate and removed all technical content. Security teams should reference CVE-2026-85984 instead, which is the authoritative record for the underlying vulnerability.
Rejected CVEs do not describe active security issues. They exist in the National Vulnerability Database (NVD) to prevent accidental reuse of the identifier and to redirect users to the correct record.
Critical Impact
No action is required for CVE-2026-87122 itself. Consult CVE-2026-85984 for the technical details, affected products, and remediation guidance.
Affected Products
- Not Available — this CVE identifier has been rejected and contains no product data
- Refer to CVE-2026-85984 for the authoritative affected product list
- No CPE URIs are associated with this record
Discovery Timeline
- 2026-09-11 - CVE-2026-87122 published to NVD with REJECT status
- 2026-09-11 - Last updated in NVD database
Technical Details for CVE-2026-87122
Vulnerability Analysis
CVE-2026-87122 contains no technical vulnerability data. The CVE Numbering Authority (CNA) rejected this identifier because it duplicates a prior reservation tracked under CVE-2026-85984. The MITRE CVE Program removes all references and descriptions from rejected candidates to prevent accidental usage in vulnerability management workflows.
Rejection typically occurs when two CVE IDs are reserved for the same underlying issue. This can happen when multiple researchers report the same flaw, or when a CNA reserves an identifier before discovering an existing entry. The consolidation preserves a single source of truth for downstream consumers.
Security practitioners scanning vendor advisories, ticketing systems, or SBOM tooling may still encounter this identifier. Treat any reference to CVE-2026-87122 as a pointer to CVE-2026-85984.
Root Cause
The root cause of the rejection is administrative. Two CVE identifiers were reserved for the same vulnerability, and the CVE Program consolidated tracking under the earlier identifier. No software defect is described in this record.
Attack Vector
No attack vector applies to CVE-2026-87122. Review CVE-2026-85984 for the exploitation details, prerequisites, and impact metrics associated with the underlying issue.
Detection Methods for CVE-2026-87122
Indicators of Compromise
- No indicators of compromise are associated with CVE-2026-87122 because the identifier carries no vulnerability data
- Detection engineering should target the indicators listed under CVE-2026-85984 instead
Detection Strategies
- Update vulnerability management pipelines to alias CVE-2026-87122 references to CVE-2026-85984
- Suppress duplicate findings in scanners that report both identifiers for the same asset
- Validate that SBOM and ticketing exports use the active identifier when communicating with vendors
Monitoring Recommendations
- Monitor the NVD feed for status changes on CVE-2026-85984, which now carries the authoritative technical detail
- Subscribe to the upstream vendor advisory once CVE-2026-85984 is enriched with product and patch data
- Audit internal knowledge base articles that reference CVE-2026-87122 and redirect them to the active record
How to Mitigate CVE-2026-87122
Immediate Actions Required
- Remove CVE-2026-87122 from active tracking queues and replace it with CVE-2026-85984
- Notify downstream teams and automated tooling that this identifier is rejected
- Consult CVE-2026-85984 for the current remediation guidance and patch availability
Patch Information
No patch information exists for CVE-2026-87122. Patch data, if any, will be published under CVE-2026-85984. Review the vendor advisory associated with that identifier before scheduling remediation work.
Workarounds
- No workarounds apply to this rejected identifier
- Follow the mitigation guidance published under CVE-2026-85984 once available
- Document the CVE-2026-87122 to CVE-2026-85984 mapping in internal vulnerability management records
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
