Faye Project maintains a focused real-time messaging and pub-sub library that, despite a narrow product footprint, serves as a communication backbone in web applications and can mediate sensitive interactions across distributed services. The durable vulnerability signal centers on its authentication and certificate-validation mechanisms, reflecting the security-critical role that a messaging intermediary plays in protecting data in transit and controlling access to published channels. Current severity, exploitation, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Faye Project over time
Signals from CVEs in this vendor scope (2 CVEs).
2 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2020-11020CRITICAL Faye (NPM, RubyGem) versions greater than 0.5.0 and before 1.0.4, 1.1.3 and 1.2.5, has the potential for authentication bypass in the extension system. The vulnerability allows any | Apr 29, 2020 | 9.8 | 30 | NO | NO |
CVE-2020-15134HIGH Faye before version 1.4.0, there is a lack of certification validation in TLS handshakes. Faye uses em-http-request and faye-websocket in the Ruby version of its client. Those libr | Jul 31, 2020 | 8.7 | 21 | NO | NO |
Signals from CVEs in this vendor scope (2 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Faye Project.
Media articles that mention a CVE ID that affects a product developed by Faye Project — matched by CVE ID, not by vendor name.