Advisory record · GHSA-2v5c-755p-p4gv

Missing TLS certificate verification in faye-websocket

CVSS 8.0 HighEPSS 0.0092 · 60th percentile

Published by the GitHub Advisory Database at 31 Jul 2020, 17:40 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
faye-websocketRubyGems<0.11.00.11.0
Identifiers
GHSA-2v5c-755p-p4gv · CVE-2020-15133
Weakness (CWE)
CWE-295
Published
31 Jul 2020
Updated
10 Sept 2026

Machine-written summary

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

Faye::WebSocket::Client in the faye-websocket package before 0.11.0 does not verify the server's TLS certificate for wss: connections. An attacker able to intercept the network path, such as a man-in-the-middle, can impersonate the server. Upgrade faye-websocket to version 0.11.0 or later; no workaround is listed, and the source says the verify_peer option only takes effect with a verifying ssl_verify_peer implementation.

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
8.0 High 3.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0092, the 60th percentile, on 9 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:16 UTC First seen by agentprime
  2. 31 Oct 2026, 15:16 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.