wget2 Improper Certificate Validation
Priority LOW 21CWE-20Published · Updated
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- High
- Impact type
- —
- Confidentiality · integrity · availability
- Low · Low · None
- Fix status
- No fix listed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA.
Summary
wget2 accepts a server certificate with incorrect Key Usage (KU) or Extended Key Usage (EKU). If the attackers compromise a certificate (with the associated private key) issued for a different purpose, they may be able to reuse it for TLS server authentication.
Why it matters now
Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00155 4th percentileScored 2026-11-07
Public exploit Yes 1 exploit referenceTagged by NVD
Fix No fix listed No fixed version in the sources yet
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
No fixed version listed by the sources yet.
Vendor assessments
Timeline
- 2026-10-02 Threatist record created from CVE-2026-1858
- 2026-10-03 Alias added: GHSA-9h5h-4q77-cphm
References
More GNU Wget2 vulnerabilities
- TI-2025-42648 Wget2: arbitrary file write via metalink path traversal in gnu wget2 CVSS 3.1CRITICAL 9.8
- TI-2025-42649 Wget2: gnu wget2: memory corruption and crash via filename sanitization logic with attacker-controlled urls CVSS 3.1HIGH 8.8
Sources
- CVE-2026-1858 · CVE Program
- CVE-2026-1858 · NVD
- FIRST EPSS
- GHSA-9h5h-4q77-cphm · GitHub Advisory Database · CC BY 4.0
- CVE-2026-1858 · Red Hat security data · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences