{
  "id": "CVE-2026-90651",
  "url": "https://poc.griffinguard.io/cve/CVE-2026-90651",
  "published_at": "2026-09-12T23:55:41.065Z",
  "vendor": "Socket",
  "product": "Socket Firewall",
  "cvss": {
    "score": 8.1,
    "source": "cna",
    "vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:H/A:L"
  },
  "kev": {
    "in_kev": false,
    "added_at": null,
    "days_after_publication": null
  },
  "first_poc": null,
  "poc_repo_count": 0,
  "exploit_count": 0,
  "suspicious_repo_count": 0,
  "edge_device": {
    "category": "Firewall / VPN",
    "confidence": "medium",
    "reason": "product or title mentions \"firewall\""
  },
  "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.",
  "cwe": "CWE-295",
  "cvss_by_source": {
    "cna": 8.1
  },
  "repos": [],
  "remediation": {
    "affected": [
      {
        "vendor": "Socket",
        "product": "Socket Firewall",
        "ranges": [
          "\u003c 2.0.0"
        ],
        "fixed_in": [
          "2.0.0"
        ]
      }
    ],
    "solutions": [
      "Upgrade to Socket Firewall 2.0.0 or later, where api_ssl_verify and upstream_ssl_verify default to true. Deployments that terminate TLS on an internal proxy or use a private CA must supply that CA via api_ssl_ca_cert / upstream_ssl_ca_cert, or explicitly disable verification for those connections."
    ],
    "upgrade": [
      "Upgrade Socket Firewall to 2.0.0 or later."
    ],
    "workarounds": [
      "On versions 1.1.334 through 1.1.x, explicitly set api_ssl_verify: true and upstream_ssl_verify: true in socket.yml. On versions before 1.1.334 this setting alone is not sufficient, because the generated nginx configuration omits lua_ssl_trusted_certificate; operators had to patch the generated configuration to inject lua_ssl_trusted_certificate and lua_ssl_verify_depth."
    ],
    "references": [
      {
        "kind": "Release notes",
        "url": "https://github.com/SocketDev/socket-registry-firewall/releases/tag/v2.0.0"
      }
    ]
  },
  "exploit_refs": [],
  "hunt_profile": [],
  "rules": []
}
