CVE-2026-90651
- Source
- https://cve.org/CVERecord?id=CVE-2026-90651
- Import Source
- https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-90651.json
- JSON Data
- https://api.osv.dev/v1/vulns/CVE-2026-90651
- Published
- 2026-09-12T23:55:41Z
- Modified
- 2026-09-14T03:46:38Z
- Severity
-
- 8.1 (High) CVSS_V3 - CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:H/A:L CVSS Calculator
- Summary
- [none]
- 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.
- 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