{"id":"CVE-2026-90651","details":"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.","modified":"2026-09-14T03:46:38.309672529Z","published":"2026-09-12T23:55:41.065Z","database_specific":{"cna_assigner":"mitre","cwe_ids":["CWE-295"],"osv_generated_from":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/90xxx/CVE-2026-90651.json"},"references":[{"type":"WEB","url":"https://docs.socket.dev/docs/registry-mode-configuration-reference"},{"type":"WEB","url":"https://github.com/SocketDev/socket-registry-firewall/releases/tag/v2.0.0"},{"type":"WEB","url":"https://hub.docker.com"},{"type":"ADVISORY","url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/90xxx/CVE-2026-90651.json"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90651"}],"affected":[{"ranges":[{"type":"GIT","repo":"https://github.com/socketdev/socket-registry-firewall","events":[{"introduced":"0"},{"fixed":"cda1991c0e93504d58ceb9d9ad57229ca6396eeb"}],"database_specific":{"source":"AFFECTED_FIELD","extracted_events":[{"introduced":"0"},{"fixed":"2.0.0"}]}}],"versions":["v1.1.344","v1.1.343","v1.1.341","v1.1.337","v1.1.336","v1.1.335","v1.1.334","v1.1.333","v1.1.332","v1.1.328","v1.1.327","v1.1.326","v1.1.323","v1.1.322","v1.1.321","v1.1.316","v1.1.312","v1.1.308","v1.1.306","v1.1.303","v1.1.301","v1.1.290","v1.1.289","v1.1.273","v1.1.265","v1.1.263","v1.1.262","v1.1.258","v1.1.254","v1.1.249","v1.1.247","v1.1.242","v1.1.230","v1.1.226","v1.1.224","v1.1.218","v1.1.212","v1.1.177","v1.1.176","v1.1.151","v1.1.139","v1.1.136","v1.1.135","v1.1.134","v1.1.133","v1.1.131","v1.1.128","v1.1.126","v1.1.125","v1.1.124","v1.1.114","v1.1.112","v1.1.111","v1.1.110","v1.1.109","v1.1.108","v1.1.104","v1.1.101","v1.1.94","v1.1.85","v1.1.73","v1.1.72"],"database_specific":{"source":"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-90651.json"}}],"schema_version":"1.9.0","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:H/A:L"}]}