ubuntu-cve-2026-69248
Vulnerability from osv_ubuntu
Published
2026-08-04 00:00
Modified
2026-08-04 00:00
Summary
Details
cryptography is a package designed to expose cryptographic primitives and recipes to Python developers. Prior to 49.0.0, if an intermediate constrained CA permits the DNS name foo.example.com, and the leaf certificate has a wildcard in its DNS SAN of .example.com, python-cryptography's verifier accepts which allows escaping outside of the permitted names. The core issue is in DNSConstraint::matches, where a wildcard pattern was treated as matching a more-specific permitted constraint even though .example.com can expand to sibling names such as bar.example.com outside foo.example.com. This allows acceptance of an invalid certificate chain. This issue is fixed in 49.0.0.
Severity
N/A (UNKNOWN)
References
{
"affected": [
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "python-cryptography",
"binary_version": "1.2.3-1ubuntu0.3+esm3"
},
{
"binary_name": "python3-cryptography",
"binary_version": "1.2.3-1ubuntu0.3+esm3"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:16.04:LTS",
"name": "python-cryptography",
"purl": "pkg:deb/ubuntu/python-cryptography@1.2.3-1ubuntu0.3+esm3?arch=source\u0026distro=esm-infra/xenial"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.0.1-1ubuntu1",
"1.0.2-1",
"1.1-1",
"1.1.1-1",
"1.1.1-1ubuntu1",
"1.1.1-1ubuntu2",
"1.1.1-1ubuntu3",
"1.2.2-2",
"1.2.3-1",
"1.2.3-1ubuntu0.1",
"1.2.3-1ubuntu0.2",
"1.2.3-1ubuntu0.3",
"1.2.3-1ubuntu0.3+esm1",
"1.2.3-1ubuntu0.3+esm3"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "python-cryptography",
"binary_version": "2.1.4-1ubuntu1.4+esm3"
},
{
"binary_name": "python3-cryptography",
"binary_version": "2.1.4-1ubuntu1.4+esm3"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:18.04:LTS",
"name": "python-cryptography",
"purl": "pkg:deb/ubuntu/python-cryptography@2.1.4-1ubuntu1.4+esm3?arch=source\u0026distro=esm-infra/bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.9-1",
"2.1.3-3",
"2.1.4-1",
"2.1.4-1build1",
"2.1.4-1build2",
"2.1.4-1ubuntu1",
"2.1.4-1ubuntu1.1",
"2.1.4-1ubuntu1.2",
"2.1.4-1ubuntu1.3",
"2.1.4-1ubuntu1.4",
"2.1.4-1ubuntu1.4+esm1",
"2.1.4-1ubuntu1.4+esm3"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "python-cryptography",
"binary_version": "2.8-3ubuntu0.3+esm2"
},
{
"binary_name": "python3-cryptography",
"binary_version": "2.8-3ubuntu0.3+esm2"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:20.04:LTS",
"name": "python-cryptography",
"purl": "pkg:deb/ubuntu/python-cryptography@2.8-3ubuntu0.3+esm2?arch=source\u0026distro=esm-infra/focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"2.6.1-3.1",
"2.6.1-4",
"2.6.1-4ubuntu1",
"2.8-1ubuntu2",
"2.8-2",
"2.8-3",
"2.8-3ubuntu0.1",
"2.8-3ubuntu0.2",
"2.8-3ubuntu0.3",
"2.8-3ubuntu0.3+esm2"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "python3-cryptography",
"binary_version": "3.4.8-1ubuntu2.4"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "python-cryptography",
"purl": "pkg:deb/ubuntu/python-cryptography@3.4.8-1ubuntu2.4?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"3.3.2-1",
"3.3.2-1build1",
"3.4.8-1",
"3.4.8-1ubuntu1",
"3.4.8-1ubuntu2",
"3.4.8-1ubuntu2.1",
"3.4.8-1ubuntu2.2",
"3.4.8-1ubuntu2.3",
"3.4.8-1ubuntu2.4"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "python3-cryptography",
"binary_version": "41.0.7-4ubuntu0.4"
}
]
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "python-cryptography",
"purl": "pkg:deb/ubuntu/python-cryptography@41.0.7-4ubuntu0.4?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"38.0.4-4",
"38.0.4-4ubuntu1",
"41.0.7-3",
"41.0.7-4build2",
"41.0.7-4build3",
"41.0.7-4ubuntu0.1",
"41.0.7-4ubuntu0.3",
"41.0.7-4ubuntu0.4"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "python3-cryptography",
"binary_version": "46.0.5-1ubuntu2"
}
]
},
"package": {
"ecosystem": "Ubuntu:26.04:LTS",
"name": "python-cryptography",
"purl": "pkg:deb/ubuntu/python-cryptography@46.0.5-1ubuntu2?arch=source\u0026distro=resolute"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"43.0.0-1ubuntu1",
"46.0.1-1ubuntu2",
"46.0.5-1ubuntu1",
"46.0.5-1ubuntu2"
]
}
],
"aliases": [],
"details": "cryptography is a package designed to expose cryptographic primitives and recipes to Python developers. Prior to 49.0.0, if an intermediate constrained CA permits the DNS name foo.example.com, and the leaf certificate has a wildcard in its DNS SAN of *.example.com, python-cryptography\u0027s verifier accepts which allows escaping outside of the permitted names. The core issue is in DNSConstraint::matches, where a wildcard pattern was treated as matching a more-specific permitted constraint even though *.example.com can expand to sibling names such as bar.example.com outside foo.example.com. This allows acceptance of an invalid certificate chain. This issue is fixed in 49.0.0.",
"id": "UBUNTU-CVE-2026-69248",
"modified": "2026-08-04T00:00:00Z",
"published": "2026-08-04T00:00:00Z",
"references": [
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2026-69248"
},
{
"type": "REPORT",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-69248"
},
{
"type": "REPORT",
"url": "https://github.com/pyca/cryptography/security/advisories/GHSA-m2h6-j472-rp4c"
},
{
"type": "REPORT",
"url": "https://github.com/pyca/cryptography/pull/14888"
},
{
"type": "REPORT",
"url": "https://github.com/pyca/cryptography/commit/4d035a4225965edeffd312079a510ef25fcfdcb2"
}
],
"related": [],
"schema_version": "1.7.0",
"severity": [
{
"score": "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N/E:P",
"type": "CVSS_V4"
},
{
"score": "medium",
"type": "Ubuntu"
}
],
"upstream": [
"CVE-2026-69248"
]
}
Loading…
Loading…
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
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.
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
Loading…
Loading…