CVE-2026-90651 Security feature bypass in Socket Firewall
Attackers can intercept traffic and modify package content or firewall decisions due to disabled TLS verification by default in Socket Firewall.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-90651?
CVE-2026-90651 is a high-severity vulnerability in Socket Firewall, published on 12 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official 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.
Weakness: CWE-295
Which versions are affected by CVE-2026-90651?
How do I fix CVE-2026-90651?
No fix has been published for CVE-2026-90651 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-90651 being exploited?
There is no known exploitation of CVE-2026-90651 in the wild and no public exploit code.
Sources
Also known as GHSA-jrp2-p3px-f5p5.