CVE-2026-90651
Received Received - Intake

Socket Firewall Missing TLS Certificate Verification

Publication date: 2026-09-13

Last updated on: 2026-09-13

Assigner: MITRE

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-13
Last Modified
2026-09-13
Generated
2026-09-14
AI Q&A
2026-09-13
EPSS Evaluated
N/A
NVD
CVE-2026-90651
EUVD
EUVD-2026-76925

Affected Vendors & Products

Showing 3 associated CPEs
Vendor Product Version / Range
socketdev socket-registry-firewall to 2.0.0 (exc)
socketdev socket-registry-firewall 1.1.334
socketdev socket-registry-firewall 2.0.0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-295 The product does not validate, or incorrectly validates, a certificate.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

Socket Firewall before version 2.0.0 does not verify upstream TLS certificates by default. When configuration keys are omitted, it sets SSL verification to false, allowing any certificate including self-signed ones. This enables attackers to intercept traffic and modify responses or package content.

Detection Guidance

Check if api_ssl_verify and upstream_ssl_verify are set to false in socket.yml. Inspect the generated nginx configuration for missing lua_ssl_trusted_certificate directives. Monitor for unexpected certificate validation failures or proxy interruptions.

Impact Analysis

An attacker could intercept communications between Socket Firewall and the Socket API or upstream registries. They might substitute malicious package content or alter firewall decisions. This could lead to unauthorized code execution or data breaches.

Compliance Impact

This vulnerability could lead to data breaches or unauthorized access, violating GDPR and HIPAA requirements for data protection and integrity. Non-compliance risks include legal penalties and reputational damage.

Mitigation Strategies
  • Update Socket Firewall to version 2.0.0 or later to enable default TLS verification.
  • Set api_ssl_verify: true and upstream_ssl_verify: true in socket.yml if using an older version.
  • For environments with proxies or self-signed certificates, import custom CA certificates or configure exceptions carefully.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-90651. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart