https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-04T17:15:32.621464+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/certfr-2026-avi-0698 certfr-2026-avi-0698 — De multiples vulnérabilités ont été découvertes dans les produits IBM. Certaines d'entre elles permettent à un attaquan… 2026-10-04T17:15:32.634673+00:00 certfr-2026-avi-0698 https://cve.radiocsirt.org/vuln/cleanstart-2026-aj39907 Withdrawn: CLEANSTART-2026-AJ39907 — gRPC-Go is the Go language implementation of gRPC 2026-10-04T17:15:32.634713+00:00

Withdrawn by the publisher.

Affected: CleanStart: step

Multiple security vulnerabilities affect the step package. gRPC-Go is the Go language implementation of gRPC. See references for individual vulnerability details.

 https://cve.radiocsirt.org/vuln/euvd-2026-267656 EUVD-2026-267656 2026-10-04T17:15:32.634744+00:00 EUVD-2026-267656 https://cve.radiocsirt.org/vuln/fkie_cve-2026-25793 fkie_cve-2026-25793 2026-10-04T17:15:32.634757+00:00

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.

 https://cve.radiocsirt.org/vuln/ghsa-69x3-g4r3-p962 GHSA-69x3-g4r3-p962 — Blocklist Bypass possible via ECDSA Signature Malleability 2026-10-04T17:15:32.634779+00:00

Affected: Go: github.com/slackhq/nebula

### 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.