CVE-2026-90651

HIGHPre-NVD 8.18.1—
EchelonGraph scoreHIGH confidence

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-09-13. a secondary CVSS source baseline 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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 v3
8.1
EG Score
8.1(high)
EG Risk
37(Track)
EG Risk 37/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity81% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
9%
KEV
Not listed

Published

September 12, 2026

Last Modified

September 14, 2026

Advisory Details (2)

Auto-updated Sep 13, 2026
Patch available. Sources: github_release.
github_release Patch Available

v2.0.0

Patch available: SocketDev/socket-registry-firewall v2.0.0

https://github.com/SocketDev/socket-registry-firewall/releases/tag/v2.0.0
generic

Configuration Reference

https://docs.socket.dev/docs/registry-mode-configuration-reference

Vendor Advisories for CVE-2026-90651(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 29× in last 7d / 34× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-20 20:16 UTCEPSS rescore
  2. 2026-09-20 17:18 UTCGHSA enrichment
  3. 2026-09-20 04:24 UTCEG score recompute
  4. 2026-09-20 04:24 UTCGHSA enrichment
  5. 2026-09-19 15:30 UTCGHSA enrichment
  6. 2026-09-19 02:33 UTCEG score recompute
  7. 2026-09-19 02:33 UTCGHSA enrichment
  8. 2026-09-18 19:28 UTCEPSS rescore
  9. 2026-09-18 13:39 UTCGHSA enrichment
  10. 2026-09-18 00:45 UTCEG score recompute
  11. 2026-09-18 00:45 UTCGHSA enrichment
  12. 2026-09-17 19:32 UTCEPSS rescore
  13. 2026-09-17 11:51 UTCGHSA enrichment
  14. 2026-09-16 22:57 UTCEG score recompute
  15. 2026-09-16 22:57 UTCGHSA enrichment
  16. 2026-09-16 14:09 UTCEPSS rescore
  17. 2026-09-16 10:03 UTCEG score recompute
  18. 2026-09-16 10:03 UTCGHSA enrichment
  19. 2026-09-16 05:15 UTCEPSS rescore
  20. 2026-09-15 21:09 UTCGHSA enrichment
  21. 2026-09-15 08:15 UTCEG score recompute
  22. 2026-09-15 08:15 UTCGHSA enrichment
  23. 2026-09-15 03:12 UTCEPSS rescore
  24. 2026-09-14 19:21 UTCEG score recompute
  25. 2026-09-14 19:21 UTCGHSA enrichment
Show 9 more
  1. 2026-09-14 18:28 UTCEG score recompute
  2. 2026-09-14 18:28 UTCGHSA enrichment
  3. 2026-09-14 15:01 UTCGHSA enrichment
  4. 2026-09-14 02:07 UTCGHSA enrichment
  5. 2026-09-13 13:13 UTCEG score recompute
  6. 2026-09-13 13:13 UTCGHSA enrichment
  7. 2026-09-13 00:19 UTCEG score recompute
  8. 2026-09-13 00:02 UTCEG score recompute
  9. 2026-09-13 00:02 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-90651?
CVE-2026-90651 is a high vulnerability published on September 12, 2026. Socket Firewall (socketdev/socket-registry-firewall) in registry mode before 2.0.0 does not verify upstream TLS certificates by default. When the apisslverify and upstreamsslverify configuration keys are omitted from socket.yml, the generated configuration sets SOCKETAPISSLVERIFY='false' and…
When was CVE-2026-90651 disclosed?
CVE-2026-90651 was first published in the National Vulnerability Database on September 12, 2026, with the most recent update on September 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-90651 actively exploited?
CVE-2026-90651 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 91.2% of all scored CVEs.
What is the CVSS score of CVE-2026-90651?
CVE-2026-90651 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-90651?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-90651, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-90651

Explore →

Is Your Infrastructure Affected by CVE-2026-90651?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs