English edition · cyberattaques.org in FrenchFrançais
VulnerabilityPatch available

OpenSSL fixes several flaws that allow remote denial of service

CERT-FR has reported several vulnerabilities in OpenSSL that let a remote attacker cause a denial of service. The 3.5.x, 4.0.x and 4.1.x branches are affected, which reaches the many servers and applications built on the library.

What to do now Illustration photo (computer code dark)
CVSS severity7.7High
EPSS probability0 %
ExploitationNot observed
PatchAvailable
Product
OpenSSL
Affected versions
OpenSSL 3.5.x before 3.5.10, 4.0.x before 4.0.4, 4.1.x before 4.1.1
Fixed in
3.5.10, 4.0.4, 4.1.1
CVE
CVE-2026-107493

CERT-FR issued advisory CERTFR-2026-AVI-1554 on 17 November 2026. It covers multiple vulnerabilities in OpenSSL, the cryptographic library behind a large share of TLS services, web servers and networked applications.

According to the advisory, an attacker can exploit these flaws remotely to cause a denial of service. The bulletin does not explain how the vulnerabilities work, and it does not say whether they are being exploited.

Three identifiers are listed: CVE-2026-107493, CVE-2026-124709 and CVE-2026-35190. Affected releases are OpenSSL 3.5.x before 3.5.10, 4.0.x before 4.0.4 and 4.1.x before 4.1.1.

For the fixes, CERT-FR points readers to OpenSSL's own security advisory published the same day. Versions 3.5.10, 4.0.4 and 4.1.1 are the cut-off points given in the advisory.

OpenSSL is often bundled into operating systems, appliances and third-party software. Administrators should therefore track updates from their distributions and vendors, not only the copies of OpenSSL they installed themselves.

Action plan

What to do now

  1. Identify systems and applications running OpenSSL 3.5.x, 4.0.x or 4.1.x, including copies embedded in third-party products.
  2. Upgrade to OpenSSL 3.5.10, 4.0.4 or 4.1.1 depending on your branch, starting with internet-facing services.
  3. Check the OpenSSL advisory of 17 November 2026 and your distribution and vendor advisories for patched packages.
  4. As general good practice, restart services that load the library after updating so the fixed version is actually in use.

Sources