Package substitution via disabled certificate validation
Published Sep 12, 2026 · Updated Sep 12, 2026
Improper TLS certificate validation in Socket Firewall before 2.0.0 allows man-in-the-middle attackers to alter upstream responses. When both verification keys are omitted, the generated configuration disables certificate checks and the Lua client accepts untrusted chains. Exploitation requires control of the network path to the Socket API or a package registry and permits package substitution or policy-decision tampering.
Summary
What happened
Improper TLS certificate validation in Socket Firewall before 2.0.0 allows man-in-the-middle attackers to alter upstream responses. When both verification keys are omitted, the generated configuration disables certificate checks and the Lua client accepts untrusted chains. Exploitation requires control of the network path to the Socket API or a package registry and permits package substitution or policy-decision tampering.
The record
- CVE
- CVE-2026-90651
- Published
- Sep 12, 2026
- Updated
- Sep 12, 2026
- Vendor
- Socket
- Product
- Socket Firewall
- Classifications
- T1557
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 12, 2026CVE publishedPublication date reported by the CVE source.
- Sep 12, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <2.0.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo