Advisory record · GHSA-mmjf-f5jw-w72q

Invalid handling of `X509_verify_cert()` internal errors in libssl

CVSS 7.5 HighCriticalEPSS 0.50 · 98th percentile

Critical, because:

  • CVSS score 7.5 (7.0 or more) and EPSS 0.50 (0.1 or more): a high score and a real chance of exploitation in the next 30 days.

How we decide what’s critical

Published by the GitHub Advisory Database at 15 Dec 2021, 00:00 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
openssl-srccrates.io>=300.0.0, <300.0.4300.0.4
Identifiers
GHSA-mmjf-f5jw-w72q · BIT-node-2021-4044 · BIT-node-min-2021-4044 · CVE-2021-4044 · RUSTSEC-2021-0129
Weakness (CWE)
CWE-835
Published
15 Dec 2021
Updated
16 Dec 2024

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

The openssl-src crate versions 300.0.0 up to but not including 300.0.4 are affected. The issue lies in how libssl handles an internal error from X509_verify_cert() during client-side certificate verification, which can make SSL_get_error() return an unexpected value and cause the application to crash or loop. An attacker controlling a server that the client connects to could trigger this, possibly with a valid certificate chain. Upgrade to openssl-src 300.0.4 or later.

Written 8 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
7.5 High 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H GitHub Advisory Database
  • CISA KEV Not listed.
  • EPSS 0.50, the 98th percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:20 UTC First seen by agentprime
  2. 31 Oct 2026, 15:20 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.