ubuntu-cve-2026-33308
Vulnerability from osv_ubuntu
Mod_gnutls is a TLS module for Apache HTTPD based on GnuTLS. Prior to version 0.13.0, code for client certificate verification did not check the key purpose as set in the Extended Key Usage extension. An attacker with access to the private key for a valid certificate issued by a CA trusted for TLS client authentication but designated for a different purpose could have used that certificate to improperly access resources requiring TLS client authentication. Server configurations that do not use client certificates (GnuTLSClientVerify ignore, the default) are not affected. The problem has been fixed in version 0.13.0 by rewriting certificate verification to use gnutls_certificate_verify_peers(), and requiring key purpose id-kp-clientAuth (also known as tls_www_client in GnuTLS) by default if the Extended Key Usage extension is present. The new GnuTLSClientKeyPurpose option allows overriding the expected key purpose if needed (please see the manual for details). Behavior for certificates without an Extended Key Usage extension is unchanged. If dedicated (sub-)CAs are used for issuing TLS client certificates only (not for any other purposes) the issue has no practical impact.
{
"affected": [
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libapache2-mod-gnutls",
"binary_version": "0.7.3-0ubuntu1"
}
]
},
"package": {
"ecosystem": "Ubuntu:16.04:LTS",
"name": "mod-gnutls",
"purl": "pkg:deb/ubuntu/mod-gnutls@0.7.3-0ubuntu1?arch=source\u0026distro=xenial"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.6-1.1",
"0.7.3-0ubuntu1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libapache2-mod-gnutls",
"binary_version": "0.8.2-3ubuntu1"
}
]
},
"package": {
"ecosystem": "Ubuntu:18.04:LTS",
"name": "mod-gnutls",
"purl": "pkg:deb/ubuntu/mod-gnutls@0.8.2-3ubuntu1?arch=source\u0026distro=bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.8.2-3ubuntu1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libapache2-mod-gnutls",
"binary_version": "0.9.0-1.1ubuntu1"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "mod-gnutls",
"purl": "pkg:deb/ubuntu/mod-gnutls@0.9.0-1.1ubuntu1?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.8.2-3ubuntu1",
"0.9.0-1.1ubuntu1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libapache2-mod-gnutls",
"binary_version": "0.9.0-1.1ubuntu1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "mod-gnutls",
"purl": "pkg:deb/ubuntu/mod-gnutls@0.9.0-1.1ubuntu1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.9.0-1.1ubuntu1"
]
}
],
"aliases": [],
"details": "Mod_gnutls is a TLS module for Apache HTTPD based on GnuTLS. Prior to version 0.13.0, code for client certificate verification did not check the key purpose as set in the Extended Key Usage extension. An attacker with access to the private key for a valid certificate issued by a CA trusted for TLS client authentication but designated for a different purpose could have used that certificate to improperly access resources requiring TLS client authentication. Server configurations that do not use client certificates (`GnuTLSClientVerify ignore`, the default) are not affected. The problem has been fixed in version 0.13.0 by rewriting certificate verification to use `gnutls_certificate_verify_peers()`, and requiring key purpose id-kp-clientAuth (also known as `tls_www_client` in GnuTLS) by default if the Extended Key Usage extension is present. The new `GnuTLSClientKeyPurpose` option allows overriding the expected key purpose if needed (please see the manual for details). Behavior for certificates without an Extended Key Usage extension is unchanged. If dedicated (sub-)CAs are used for issuing TLS client certificates only (not for any other purposes) the issue has no practical impact.",
"id": "UBUNTU-CVE-2026-33308",
"modified": "2026-04-02T17:31:26Z",
"published": "2026-03-24T03:16:00Z",
"references": [
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2026-33308"
},
{
"type": "REPORT",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-33308"
},
{
"type": "REPORT",
"url": "https://github.com/airtower-luna/mod_gnutls/security/advisories/GHSA-hm2g-m958-8qgh"
}
],
"related": [],
"schema_version": "1.7.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N",
"type": "CVSS_V3"
},
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
},
{
"score": "medium",
"type": "Ubuntu"
}
],
"upstream": [
"CVE-2026-33308"
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.