Is openssl affected by CVE-2018-16395?

RubyGems openssl is affected in =2.1.0 <2.1.2.

Is CVE-2018-16395 being exploited?

Not on the CISA KEV list. EPSS exploit probability is 10.7%.

critical

CVE-2018-16395

Q: Is CVE-2018-16395 being exploited?

Not on the CISA KEV list. EPSS exploit probability is 10.7%.

RubyGems · openssl

Summary

Ruby Openssl Allows Incorrect Value Comparison

Severity: critical
EPSS: 10.7% (p95)
Also known as: GHSA-mmrq-6999-72v8
Published: 2022-05-13

References

https://nvd.nist.gov/vuln/detail/CVE-2018-16395
https://github.com/ruby/openssl/commit/f653cfa43f0f20e8c440122ea982382b6228e7f5
https://hackerone.com/reports/387250

Related advisories

CVE-2026-42327 — high · crates.io/openssl
CVE-2026-41676 — high · crates.io/openssl
CVE-2026-41678 — high · crates.io/openssl
CVE-2026-41681 — high · crates.io/openssl
CVE-2026-41898 — high · crates.io/openssl
GHSA-9qwg-crg9-m2vc — high · crates.io/openssl
GHSA-6hcf-g6gr-hhcr — high · crates.io/openssl
CVE-2017-14033 — high · RubyGems/openssl

Is your project exposed to this? Stateward checks every dependency on every pull request and flags it only if your code actually reaches it.

Check my repo

Summarize with AI

ChatGPT Claude Perplexity

Sources: CISA KEV (public domain), OSV.dev & GitHub Advisory Database (CC-BY-4.0), FIRST EPSS, NVD/CWE (public domain). Served live from the Stateward advisory database.