Skip to content

CVE-2025-66478

Rejected reason: This CVE is a duplicate of CVE-2025-55182.

This CVE has been withdrawn. NVD marks this identifier as Rejected, which means it was a duplicate or turned out not to be a vulnerability. The analysis below is kept for reference only — do not act on it.

CVSS
Not scored yetNVD has not published a score
Exploited in the wild
Not knownPublic exploit code; not in CISA KEV
EPSS
No score yet
Fix
Not stated by the vendorno fixed release in the CVE record
Published
3 Dec 2025analysed here 12 Nov 2026

NVD hasn't published a CVSS score for this CVE yet. Severity and the CVSS vector appear here once it is scored upstream.

Fix and mitigation

Remediation steps (AI-written)

Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.

Exploitation evidence

CISA KEV catalog
Not listed as of our last sync.
Public exploit code
Yes: 1 Metasploit module · 25 GitHub proofs of concept

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

Timeline

  1. 1 Oct 2025First public exploit or proof of concept
  2. 3 Dec 2025CVE record last updated64 days (about 2 months) later
  3. 3 Dec 2025Publishedsame day later
  4. 12 Nov 2026Analysed by vulneraibility.com344 days (about 11 months) later

References

NVDCVE.orgCVE DetailsSource

Where the data on this page comes from

Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

Similar CVEs

Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.

© 2026 vulneraibility.com