{"id":"CVE-2026-90651","title":"Socket Firewall (socketdev/socket-registry-firewall) in registry mode before 2.0.0 does not verify upstream TLS certificates by default","summary":"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 …","severity":"high","cvss":8.1,"cvssVector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:H/A:L","cwe":["CWE-295"],"vendor":"Socket","product":"socketdev/socket-registry-firewall","affected":["socketdev/socket-registry-firewall < 2.0.0"],"published":"2026-09-13","updated":"2026-09-14","sourceUpdated":"2026-09-14T19:18:07.567","source":"NVD","sourceUrl":"https://nvd.nist.gov/vuln/detail/CVE-2026-90651","references":[{"url":"https://docs.socket.dev/docs/registry-mode-configuration-reference","label":"cve@mitre.org"},{"url":"https://github.com/SocketDev/socket-registry-firewall/releases/tag/v2.0.0","label":"cve@mitre.org"}],"tags":["nvd","cve.org"],"ssvc":{"exploitation":"none","automatable":"no","technicalImpact":"partial","timestamp":"2026-09-14T14:56:54.408892Z"},"ingestedAt":"2026-09-14T15:23:07.477Z","epss":0.00189,"epssPercentile":0.08734,"slug":"CVE-2026-90651","body":"## Overview\n\nSocket 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.\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.","depth":"twilight","depthScore":45,"depthScoreParts":{"impact":44.6,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[]}