CVE-2026-69248

cryptography is a package designed to expose cryptographic primitives and recipes to Python developers. In versions 45.0.0 through 48.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.

CVSS

No CVSS.

References

Link	Resource
https://github.com/pyca/cryptography/commit/4d035a4225965edeffd312079a510ef25fcfdcb2
https://github.com/pyca/cryptography/pull/14888
https://github.com/pyca/cryptography/security/advisories/GHSA-m2h6-j472-rp4c
https://github.com/pyca/cryptography/security/advisories/GHSA-m2h6-j472-rp4c

Configurations

No configuration.

History

23 Oct 2026, 21:10

Type	Values Removed	Values Added
Summary		(es) criptografía es un paquete diseñado para exponer primitivas y recetas criptográficas a los desarrolladores de Python. Antes de 49.0.0, si una CA intermedia restringida permite el nombre DNS foo.example.com, y el certificado hoja tiene un comodín en su SAN DNS de .example.com, el verificador de python-cryptography lo acepta, lo que permite escapar fuera de los nombres permitidos. El problema principal está en DNSConstraint::matches, donde un patrón de comodín fue tratado como coincidente con una restricción permitida más específica, a pesar de que .example.com puede expandirse a nombres hermanos como bar.example.com fuera de foo.example.com. Esto permite la aceptación de una cadena de certificados no válida. Este problema está solucionado en 49.0.0.

Information

Published : 2026-08-03 22:16

Updated : 2026-10-23 21:10

NVD link : CVE-2026-69248

Mitre link : CVE-2026-69248

CVE.ORG link : CVE-2026-69248

JSON object : View

Products Affected

No product.

CWE

CWE-295

Improper Certificate Validation

{"id": "CVE-2026-69248", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-69248", "role": "CISA Coordinator", "options": [{"exploitation": "poc"}, {"automatable": "no"}, {"technicalImpact": "partial"}], "version": "2.0.3", "timestamp": "2026-08-04T13:34:32.304052Z"}}], "cvssMetricV40": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"Safety": "NOT_DEFINED", "version": "4.0", "Recovery": "NOT_DEFINED", "baseScore": 6.9, "Automatable": "NOT_DEFINED", "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "valueDensity": "NOT_DEFINED", "vectorString": "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/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X", "exploitMaturity": "PROOF_OF_CONCEPT", "providerUrgency": "NOT_DEFINED", "userInteraction": "NONE", "attackComplexity": "LOW", "attackRequirements": "PRESENT", "privilegesRequired": "NONE", "subIntegrityImpact": "NONE", "vulnIntegrityImpact": "HIGH", "integrityRequirement": "NOT_DEFINED", "modifiedAttackVector": "NOT_DEFINED", "subAvailabilityImpact": "NONE", "vulnAvailabilityImpact": "NONE", "availabilityRequirement": "NOT_DEFINED", "modifiedUserInteraction": "NOT_DEFINED", "modifiedAttackComplexity": "NOT_DEFINED", "subConfidentialityImpact": "NONE", "vulnConfidentialityImpact": "LOW", "confidentialityRequirement": "NOT_DEFINED", "modifiedAttackRequirements": "NOT_DEFINED", "modifiedPrivilegesRequired": "NOT_DEFINED", "modifiedSubIntegrityImpact": "NOT_DEFINED", "modifiedVulnIntegrityImpact": "NOT_DEFINED", "vulnerabilityResponseEffort": "NOT_DEFINED", "modifiedSubAvailabilityImpact": "NOT_DEFINED", "modifiedVulnAvailabilityImpact": "NOT_DEFINED", "modifiedSubConfidentialityImpact": "NOT_DEFINED", "modifiedVulnConfidentialityImpact": "NOT_DEFINED"}}]}, "affected": [{"source": "security-advisories@github.com", "affectedData": [{"vendor": "pyca", "product": "cryptography", "versions": [{"status": "affected", "version": "< 49.0.0"}]}]}], "published": "2026-08-03T22:16:52.550", "references": [{"url": "https://github.com/pyca/cryptography/commit/4d035a4225965edeffd312079a510ef25fcfdcb2", "source": "security-advisories@github.com"}, {"url": "https://github.com/pyca/cryptography/pull/14888", "source": "security-advisories@github.com"}, {"url": "https://github.com/pyca/cryptography/security/advisories/GHSA-m2h6-j472-rp4c", "source": "security-advisories@github.com"}, {"url": "https://github.com/pyca/cryptography/security/advisories/GHSA-m2h6-j472-rp4c", "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-295"}]}], "descriptions": [{"lang": "en", "value": "cryptography is a package designed to expose cryptographic primitives and recipes to Python developers. In versions 45.0.0 through 48.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."}, {"lang": "es", "value": "criptograf\u00eda es un paquete dise\u00f1ado para exponer primitivas y recetas criptogr\u00e1ficas a los desarrolladores de Python. Antes de 49.0.0, si una CA intermedia restringida permite el nombre DNS foo.example.com, y el certificado hoja tiene un comod\u00edn en su SAN DNS de *.example.com, el verificador de python-cryptography lo acepta, lo que permite escapar fuera de los nombres permitidos. El problema principal est\u00e1 en DNSConstraint::matches, donde un patr\u00f3n de comod\u00edn fue tratado como coincidente con una restricci\u00f3n permitida m\u00e1s espec\u00edfica, a pesar de que *.example.com puede expandirse a nombres hermanos como bar.example.com fuera de foo.example.com. Esto permite la aceptaci\u00f3n de una cadena de certificados no v\u00e1lida. Este problema est\u00e1 solucionado en 49.0.0."}], "lastModified": "2026-10-23T21:10:00.157", "sourceIdentifier": "security-advisories@github.com"}