CVE-2026-8367

aria2c Improper Certificate Validation

Published May 13, 2026 CVSS 3.1 · 4.8 Medium EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

aria2c accepts a server certificate that contains an incorrect Extended Key Usage, allowing an attacker who has compromised such a certificate, along with its private key, to reuse it for TLS server authentication. This flaw can lead the client to trust the attacker as a legitimate server, potentially enabling a man‑in‑the‑middle attack, data exfiltration, or injection of malicious content. The primary impact is an authentication bypass that undermines the confidentiality and integrity guarantees of TLS connections used by aria2c.

Affected Systems

The vulnerability affects all versions of aria2c distributed by the aria2 Project. No specific versions are listed as affected, and no version restrictions are currently known.

Risk and Exploitability

The CVSS score of 4.8 categorizes the weakness as moderate and the EPSS score is not available, indicating a low to moderate risk of exploitation under typical conditions. The flaw requires an attacker to have already compromised a certificate with an incorrect Extended Key Usage, so a successful attack would likely be carried out by an external attacker who also has the private key for that certificate. The vulnerability is not listed in the CISA KEV catalog, suggesting no widespread active exploitation. The attack vector would involve the attacker installing the malicious certificate on a server that a user’s aria2c connects to, allowing a man‑in‑the‑middle style compromise. While the potential impact to confidentiality and integrity is serious, the specific prerequisites reduce the likelihood of exploitation for most organizations.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade aria2c to a release that validates server certificate EKU.
  • Configure aria2c to enforce strict TLS certificate checking and reject certificates with mismatched EKU.
  • Where upgrades are unavailable, restrict aria2c to use only certificates issued by trusted authorities and consider implementing certificate pinning.

Generated by OpenCVE AI on May 13, 2026 at 17:39 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
CPEs cpe:2.3:a:aria2_project:aria2:*:*:*:*:*:*:*:*
Type Values Removed Values Added
First Time appeared Aria2 Project
Aria2 Project aria2
Vendors & Products Aria2 Project
Aria2 Project aria2
Type Values Removed Values Added
Description 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.
Title aria2c Improper Certificate Validation
Weaknesses CWE-295
References
Metrics cvssV3_1

{'score': 4.8, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N'}

Weaknesses
  • CWE-295

    Improper Certificate Validation

Sources

Status
PUBLISHED
Assigner
tenable
Published
Updated
May 13, 2026, 6:35 PM
Reserved
May 11, 2026, 8:46 PM
Status
Analyzed
Published
May 13, 2026, 4:17 PM
Modified
Oct 26, 2026, 5:10 PM