CVE-2026-23320
NoneCVSS
—
EPSS
—
Published
Mar 25, 2026
CISA due date
—
Cloudanix analysis
Monitor only
SSVC: Track
A reported security problem was later withdrawn so there is nothing to fix or worry about.
- Exploitation
- Other
- Attacker needs
- Other
- Complexity
- Theoretical
- Impact
- Other
- Component
- Other
- Class
- Other
- Remediation
- Other
- Effort
- Other
- Patch risk
- None
What it actually does
No technical impact exists because the CVE ID was rejected or withdrawn by its numbering authority.
Why it matters to the business
No business or operational consequences; the reported issue does not represent a valid vulnerability.
How an attack unfolds
Not applicable; the CVE has been rejected so no exploitation path exists.
How to fix it
No remediation or mitigation is required.
How to confirm the fix worked
Confirm the CVE remains listed as rejected in the official CVE database.
How to detect it
No exploitation could have occurred; review CVE status in public databases to confirm rejection.
What your security team should do
- Monitor official CVE sources for any future re-issuance of this identifier
- Ignore this entry in vulnerability scanners and risk assessments
The record
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
Affected packages
| Ecosystem | Package | Introduced | Fixed |
|---|