CVE-2026-90651 Details
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.
A vulnerability exists in Socket Firewall (socketdev/socket-registry-firewall) versions prior to 2.0.0, in registry mode, where the application does not verify upstream TLS certificates by default. If the 'api_ssl_verify' and 'upstream_ssl_verify' configuration keys are not specified in 'socket.yml', the default settings disable SSL verification for both the API and upstream connections. As a result, the OpenResty/Lua HTTP client accepts any certificate, including self-signed or untrusted ones, without validating the certificate chain. This flaw allows an attacker to intercept traffic between Socket Firewall and the Socket API or an upstream package registry, presenting a fraudulent certificate to modify responses in transit. Exploitation could involve injecting malicious package content or altering the allow/block decisions enforced by the firewall. While version 2.0.0 rectifies this issue by enabling verification for both settings, earlier versions required manual configuration patches to support verification effectively.
Users can upgrade to Socket Firewall version 2.0.0 or later, which defaults to verifying upstream TLS connections. For versions prior to 2.0.0, it is necessary to manually enable SSL verification and patch the nginx configuration to support it.
Metrics
CVSS 4.0 Severity and Vector Strings:
VolerionCVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
Volerion
Assessed Sep 13, 2026CISA-ADP
Assessed Sep 14, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://docs.socket.dev/docs/registry-mode-configuration-reference | [email protected] | Vendor |
| https://github.com/SocketDev/socket-registry-firewall/releases/tag/v2.0.0 | [email protected] | Release NotesVendor |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-295 | Improper Certificate Validation | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| Socket Firewall | < 2.0.0 (semver) |
CPE
Remediation
| |
Change History
2 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Sep 14, 2026 | CVE Modified | CISA-ADP |
| Sep 13, 2026 | New CVE Received | [email protected] |