cryptography is a package designed to expose cryptographic primitives and recipes to Python developers. Prior to version 46.0.6, DNS name constraints were only validated against SANs within child certificates, and not the "peer name" presented during each validation. Consequently, cryptography would allow a peer named bar.example.com to validate against a wildcard leaf certificate for *.example.com, even if the leaf's parent certificate (or upwards) contained an excluded subtree constraint for bar.example.com. This issue has been patched in version 46.0.6.

There are packages installed that are affected by a vulnerability referenced in the following CVE:

  - cryptography is a package designed to expose cryptographic primitives and recipes to Python developers.
    Prior to version 46.0.6, DNS name constraints were only validated against SANs within child certificates,
    and not the "peer name" presented during each validation. Consequently, cryptography would allow a peer
    named bar.example.com to validate against a wildcard leaf certificate for *.example.com, even if the
    leaf's parent certificate (or upwards) contained an excluded subtree constraint for bar.example.com. This
    issue has been patched in version 46.0.6. (CVE-2026-34073)

The version of IBM Cognos Analytics installed on the remote host is 12.0.4 prior to 12.0.4 FP3, or 12.1.x prior to 12.1.3 FP2. It is, therefore, affected by multiple vulnerabilities as referenced in the IBM Security Bulletin No.
7287209:

  - NLTK versions 3.9.2 and prior are vulnerable to arbitrary code execution due to improper input     validation in the StanfordSegmenter module. The module dynamically loads external Java .jar files     without verification or sandboxing. An attacker can supply or replace the JAR file, enabling the     execution of arbitrary Java bytecode at import time. (CVE-2026-0848)

  - The lodash fix for CVE-2021-23337 added validation for the variable option in _.template but did not     apply the same validation to options.imports key names. Both paths flow into the same Function()     constructor sink. When an application passes untrusted input as options.imports key names, an attacker     can inject default-parameter expressions that execute arbitrary code at template compilation time.
    (CVE-2026-4800)

  - cryptography is a package designed to expose cryptographic primitives and recipes to Python developers.
    From 45.0.0 to before 46.0.7, if a non-contiguous buffer was passed to APIs which accepted Python     buffers (e.g. Hash.update()), this could lead to buffer overflows. (CVE-2026-39892)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

There are packages installed that are affected by multiple vulnerabilities referenced in the following CVEs:

  - cryptography is a package designed to expose cryptographic primitives and recipes to Python developers.
    Prior to version 46.0.6, DNS name constraints were only validated against SANs within child certificates,
    and not the "peer name" presented during each validation. Consequently, cryptography would allow a peer
    named bar.example.com to validate against a wildcard leaf certificate for *.example.com, even if the
    leaf's parent certificate (or upwards) contained an excluded subtree constraint for bar.example.com. This
    issue has been patched in version 46.0.6. (CVE-2026-34073)

  - cryptography is a package designed to expose cryptographic primitives and recipes to Python developers.
    From 45.0.0 to before 46.0.7, if a non-contiguous buffer was passed to APIs which accepted Python buffers
    (e.g. Hash.update()), this could lead to buffer overflows. This vulnerability is fixed in 46.0.7.
    (CVE-2026-39892)

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - cryptography is a package designed to expose cryptographic primitives and recipes to Python developers.
    Prior to version 46.0.6, DNS name constraints were only validated against SANs within child certificates,     and not the peer name presented during each validation. Consequently, cryptography would allow a peer     named bar.example.com to validate against a wildcard leaf certificate for *.example.com, even if the     leaf's parent certificate (or upwards) contained an excluded subtree constraint for bar.example.com. This     issue has been patched in version 46.0.6. (CVE-2026-34073)

Note that Nessus relies on the presence of the package as reported by the vendor.

The remote Fedora 44 host has a package installed that is affected by a vulnerability as referenced in the FEDORA-2026-2423902e8b advisory.

    Update to v46.0.6

        This includes a single fix for security issue:

        * **SECURITY ISSUE**: Fixed a bug where name constraints were not applied           to peer names during verification when the leaf certificate contains a           wildcard DNS SAN. Ordinary X.509 topologies are not affected by this bug,           including those used by the Web PKI. Credit to **Oleh Konko (1seal)** for           reporting the issue. **CVE-2026-34073**

Tenable has extracted the preceding description block directly from the Fedora security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The remote Fedora 43 host has a package installed that is affected by a vulnerability as referenced in the FEDORA-2026-6c010af7be advisory.

    Update to v46.0.6

        This includes a single fix for security issue:

        * **SECURITY ISSUE**: Fixed a bug where name constraints were not applied           to peer names during verification when the leaf certificate contains a           wildcard DNS SAN. Ordinary X.509 topologies are not affected by this bug,           including those used by the Web PKI. Credit to **Oleh Konko (1seal)** for           reporting the issue. **CVE-2026-34073**


Tenable has extracted the preceding description block directly from the Fedora security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

ID	Name	Product	Family	Type	Severity
465541	Echo: cryptography: security update to 46.0.6python-cryptography: security update to 1:43.0.0-3+deb13u1+e3	Tenable Cloud Security	Echo Local Security Checks	Local	medium
465541	Echo: cryptography: security update to 46.0.6python-cryptography: security update to 1:43.0.0-3+deb13u1+e3	Tenable Self-Hosted Container Security	Echo Local Security Checks	Local	medium
347960	IBM Cognos Analytics 12.0.4 < 12.0.4 FP3 / 12.1.x < 12.1.3 FP2 Multiple Vulnerabilities (7287209)	Nessus	CGI abuses	Remote	high
440103	Alpine: multiple py3-cryptography packages: security update to 46.0.7-r0	Tenable Cloud Security	Alpine Linux Local Security Checks	Local	medium
440103	Alpine: multiple py3-cryptography packages: security update to 46.0.7-r0	Tenable Self-Hosted Container Security	Alpine Linux Local Security Checks	Local	medium
439581	SCA: security update for cryptography (GHSA-m959-cc7f-wv43)	Tenable Cloud Security	SCA Checks	Local	medium
439581	SCA: security update for cryptography (GHSA-m959-cc7f-wv43)	Tenable Self-Hosted Container Security	SCA Checks	Local	medium
304412	Linux Distros Unpatched Vulnerability : CVE-2026-34073	Nessus	Misc.	Local	medium
304258	Fedora 44 : python-cryptography (2026-2423902e8b)	Nessus	Fedora Local Security Checks	Local	medium
304255	Fedora 43 : python-cryptography (2026-6c010af7be)	Nessus	Fedora Local Security Checks	Local	medium

Detections

Analytics

CVE-2026-34073

medium

Tenable Plugins

medium

medium

high

medium

medium

medium

medium

medium

medium

medium