Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Further investigation showed that it was not a security issue; there is no indication that an applicable SSH private key has ever been compromised. Notes: none.
This CVE has been withdrawn by MITRE
MITRE marked CVE-2025-29630 as REJECTED on . It is no longer considered a valid vulnerability record. The original content below is preserved for historical reference only.
Reason given by MITRE
DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Further investigation showed that it was not a security issue; there is no indication that an applicable SSH private key has ever been compromised. Notes: none.
CVE-2025-29630
✕ Withdrawn — historical dataUNRATEDCVSS · not yet scored
—
- CVSS v3
- —
- EchelonGraph score
- Not yet assessedThis CVE record was withdrawn by its numbering authority, so there is no vulnerability to rate.
- EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- —Not applicable: this CVE ID was withdrawn
Published
July 25, 2025
Last Modified
April 3, 2026
Frequently asked(3)
What is CVE-2025-29630?
CVE-2025-29630 is a rejected CVE ID: its record was withdrawn on April 3, 2026 and no longer describes a vulnerability. Reason given: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Further investigation showed that it was not a security issue; there is no indication that an applicable SSH private key has ever been compromised. Notes: none.
When was the CVE record for CVE-2025-29630 published?
The CVE record for CVE-2025-29630 was published on July 25, 2025. EchelonGraph's copy of the record carries a last-modified date of April 3, 2026; the record at its source may have been updated since.
How do I remediate CVE-2025-29630?
There is nothing to remediate under CVE-2025-29630: it is a rejected (withdrawn) CVE ID and no longer describes a vulnerability.