CVE-2026-90651: Socket Firewall · Improper Certificate Validation
Affects Socket FirewallSource CVE Database V5
Not known to be exploited · CVSS 8.1 High : upgrade to 2.0.0 soon.
Data as of 28 Oct 2026, 05:12 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.0.0
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:H/A:LExploitation evidence
Disclosed: evidence found.
CVE published 12 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade Socket Firewall and socketdev/socket-registry-firewall to 2.0.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SocketSocket Firewall | Affected
| Fixed in
|
GitHubsocketdev/socket-registry-firewallpkg:github/socketdev/socket-registry-firewallOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade to Socket Firewall version 2.0.0 or later, which enables upstream TLS certificate verification by default. For versions prior to 2.0.0, explicitly set api_ssl_verify and upstream_ssl_verify to true in the socket.yml configuration and manually patch the generated nginx configuration to include lua_ssl_trusted_certificate if using versions before 1.1.334. This ensures proper certificate chain validation and mitigates the risk of man-in-the-middle attacks.
Description
Socket Firewall (socketdev/socket-registry-firewall) in registry mode before 2.0.0 does not verify upstream TLS certificates by default. When the api_ssl_verify and upstream_ssl_verify configuration keys are omitted from socket.yml, the generated configuration sets SOCKET_API_SSL_VERIFY='false' and UPSTREAM_SSL_VERIFY='false', and the OpenResty/Lua HTTP client used for outbound requests accepts any certificate, including self-signed and otherwise untrusted certificates, without validating the chain. An attacker positioned to intercept traffic between Socket Firewall and the Socket API or an upstream package registry can present a crafted certificate and modify responses in transit, including substituting malicious package content or altering the allow/block decisions the firewall enforces. Setting api_ssl_verify: true and upstream_ssl_verify: true enables verification; however, in versions before 1.1.334, the generated nginx configuration did not emit lua_ssl_trusted_certificate, and thus verification could not be used successfully without manually patching the generated configuration. Version 2.0.0 changes the default for both settings to true.