Severity by source
AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
Lifecycle Timeline
2DescriptionCVE.org
aria2c accepts a server certificate with incorrect 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.
AnalysisAI
aria2c fails to properly validate Extended Key Usage (EKU) constraints in TLS server certificates, allowing attackers who possess a compromised certificate issued for a different purpose to impersonate legitimate servers. This undermines certificate-based authentication and enables man-in-the-middle attacks against aria2c downloads over HTTPS, potentially leading to delivery of malicious files or interception of sensitive data.
Technical ContextAI
aria2c is a lightweight command-line download utility that supports multiple protocols including HTTPS. The vulnerability stems from improper validation of X.509 certificate Extended Key Usage (EKU) extensions during TLS server authentication. EKU is a critical X.509 extension that constrains the purposes for which a certificate's public key may be used-for example, restricting a certificate to TLS server authentication (id-kp-serverAuth) versus code signing or client authentication. The root cause (CWE-295: Improper Certificate Validation) indicates that aria2c's TLS implementation does not enforce EKU constraints, accepting any certificate with a valid signature chain regardless of its declared purpose. This means a certificate compromised from a code-signing CA, email encryption service, or other non-TLS-server purpose can be reused for fraudulent TLS server impersonation if the attacker obtains the associated private key.
RemediationAI
Apply a patched version of aria2c released by the aria2 project that properly validates EKU extensions during TLS server authentication-exact patched version numbers are not provided in available data, so consult the aria2 project's official releases and the Tenable advisory for version guidance. In the interim, minimize risk by downloading files only over trusted, isolated networks (e.g., corporate intranets with certificate pinning); restricting aria2c usage to environments where the server's identity can be independently verified out-of-band; or using aria2c with a custom CA bundle that includes only trusted root CAs known to issue certificates with correct EKU constraints. Organizations that cannot immediately patch should audit their aria2c deployments to identify which servers and URLs are routinely accessed, then apply network-level compensating controls such as TLS inspection proxies or firewall rules that enforce certificate validation-noting that such controls add latency and may interfere with legitimate server changes. The most effective near-term control is to restrict aria2c to authenticated, secured environments until patches are available.
Same weakness CWE-295 – Improper Certificate Validation
View allSame technique Information Disclosure
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-30042
GHSA-rpx3-3f8j-f6v2