Quick answers
- Is CVE-2026-67693 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-67693 being exploited in the wild.
- How severe is CVE-2026-67693?
- High severity, with a CVSS score of 7.5, published 8 October 2026.
- Which products and versions are affected?
- GnuTLS 3.8.13.
- Is there a fix for CVE-2026-67693?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-67693 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-67693?
- Check whether you run GnuTLS at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
GnuTLS 3.8.13 treats a Key Usage extension with all bits set to zero as if the extension were absent, and does not cross-check Key Usage bits when verifying Extended Key Usage purposes. An end-entity certificate with critical Key Usage cleared but Extended Key Usage containing id-kp-serverAuth is incorrectly accepted by both certtool and gnutls-cli, violating RFC 5280. The vulnerability requires a malicious or compromised certificate authority and affects deployments that rely on Key Usage policy enforcement.
Affected products
- GnuTLS GnuTLS 3.8.13
Timeline
- 2025-01: other: Issue reported upstream as #1642 but remained open without fix
- 2026-09-03: disclosed: Public disclosure via GitHub gist
- 2026-10-08: advisory