FlawAtlas
Search the atlas
CVE-2026-25793 High

Blocklist Bypass possible via ECDSA Signature Malleability in github.com/slackhq/nebula

Blocklist Bypass possible via ECDSA Signature Malleability in github.com/slackhq/nebula

Exploit probability 0.1%
Published February 17, 2026
Required by Not available
Last source change February 21, 2026

02 / AFFECTED SOFTWARE

Affected packages

Unknown Unknown

14 explicit affected versions

Go github.com/slackhq/nebula
Go github.com/slackhq/nebula

03 / CONNECTIONS

Connected vulnerabilities

related OPENSUSE-SU-2026:21483-1

04 / EVIDENCE

Source records

Open Source Vulnerabilities CVE-2026-25793

Nebula is a scalable overlay networking tool. In versions from 1.7.0 to 1.10.2, when using P256 certificates (which is not the default configuration), it is possible to evade a blocklist entry created against the fingerprint of a certificate by using ECDSA Signature Malleability to use a copy of the certificate with a different fingerprint. This issue has been patched in version 1.10.3.

View original source
Open Source Vulnerabilities GO-2026-4458

Blocklist Bypass possible via ECDSA Signature Malleability in github.com/slackhq/nebula

View original source
Open Source Vulnerabilities GHSA-69x3-g4r3-p962

### Impact When using P256 certificates (which is not the default configuration), it is possible to evade a blocklist entry created against the fingerprint of a certificate by using ECDSA Signature Malleability to use a copy of the certificate with a different fingerprint. In order for this to affect a user or network, all of the following must be true: * `CURVE_P256` certificates are being used * There are one or more entries on the blocklist * The certificates for those entries are signed by a trusted CA and not expired * An attacker has a copy of the private key, and corresponding certificate, for one of those blocklist entries ### Patches See attached ### Workarounds If full copies of each certificate on the existing blocklist are available, it is possible to compute their opposite-chirality signature, and then the appropriate second fingerprint to list in the blocklist. Rotating out all CAs that have signed hosts on the blocklist will also prevent exploitation of this vulnerability.

View original source

05 / REFERENCES

Further evidence