Blocklist bypass via alternate P256 signature
Published Feb 6, 2026 · Updated Feb 6, 2026
Improper P256 certificate validation in Slack Technologies Nebula 1.7.0 through 1.10.2 allows remote authenticated users to bypass blocklists. CAPool.VerifyCertificate accepted either valid ECDSA signature form while testing only one signature-derived certificate fingerprint against the blocklist. A P256 deployment with a nonempty blocklist, a trusted unexpired blocked certificate, and its private key lets the blocked peer rejoin the overlay.
Summary
What happened
Improper P256 certificate validation in Slack Technologies Nebula 1.7.0 through 1.10.2 allows remote authenticated users to bypass blocklists. CAPool.VerifyCertificate accepted either valid ECDSA signature form while testing only one signature-derived certificate fingerprint against the blocklist. A P256 deployment with a nonempty blocklist, a trusted unexpired blocked certificate, and its private key lets the blocked peer rejoin the overlay.
The record
- CVE
- CVE-2026-25793
- Published
- Feb 6, 2026
- Updated
- Feb 6, 2026
- Vendor
- Slack Technologies
- Product
- Nebula
- Classifications
- CWE-347, T1553
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 6, 2026CVE publishedPublication date reported by the CVE source.
- Feb 6, 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=>= 1.7.0, < 1.10.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
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