What’s Vulnerable › Vulnerabilities

CVE-2026-90651

• Severity: high (CVSS 8.1 v3.1)
• Exploited in the wild: not listed in CISA KEV
• EPSS: 0.2% probability of exploitation in the next 30 days
• Public exploit or detection template: none known
• Published: 2026-09-13 · updated 2026-09-22
• Weakness: CWE-295

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.

Affected products

• Socket Firewall: before 2.0.0 — fixed in 2.0.0

How to fix

Upgrade to a fixed version: Socket Firewall 2.0.0. Check the vendor advisory for mitigations.

References

• https://docs.socket.dev/docs/registry-mode-configuration-reference
• https://github.com/SocketDev/socket-registry-firewall/releases/tag/v2.0.0

Get alerted when CVE-2026-90651 or the next vulnerability affects your stack