<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Fri, 02 Oct 2026 14:54:13 +0000</lastBuildDate>
    <item>
      <title>ALSA-2026:64774 — Important: python3.14-cryptography security update</title>
      <link>https://cve.radiocsirt.org/vuln/alsa-2026:64774</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:9: python3.14-cryptography&lt;/p&gt;
&lt;p&gt;Python is an interpreted, interactive, object-oriented programming language, which includes modules, classes, exceptions, very high level dynamic data types and dynamic typing. Python supports interfaces to many system calls and libraries, as well as to various windowing systems.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* python-cryptography: python-cryptography: Duplicate self-signed intermediates can cause exponential path-building (CVE-2026-69249)
  * python-cryptography: python-cryptography: python-cryptography verifier accepts wildcard DNS names allowing escape from permittedSubtrees (CVE-2026-69248)&lt;/p&gt;
&lt;p&gt;For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:9: python3.14-cryptography&lt;/p&gt;
&lt;p&gt;Python is an interpreted, interactive, object-oriented programming language, which includes modules, classes, exceptions, very high level dynamic data types and dynamic typing. Python supports interfaces to many system calls and libraries, as well as to various windowing systems.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* python-cryptography: python-cryptography: Duplicate self-signed intermediates can cause exponential path-building (CVE-2026-69249)
  * python-cryptography: python-cryptography: python-cryptography verifier accepts wildcard DNS names allowing escape from permittedSubtrees (CVE-2026-69248)&lt;/p&gt;
&lt;p&gt;For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/alsa-2026:64774</guid>
    </item>
    <item>
      <title>bdu:2026-11011</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-11011</link>
      <description>bdu:2026-11011</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-11011</guid>
    </item>
    <item>
      <title>BREW-ansible@10-CVE-2026-69249 — python-cryptography: Duplicate self-signed intermediates can cause exponential path-building</title>
      <link>https://cve.radiocsirt.org/vuln/brew-ansible@10-cve-2026-69249</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: ansible@10&lt;/p&gt;
&lt;p&gt;### Summary
When resolving invalid certificate chains that include duplicate copies of self-signed certificates, the processing recursively invokes the same candidate, leading to an exponential blowup. Although the limitation that the chain depth cannot exceed a specified maximum depth prevents unbounded recursion and guarantees termination, an attacker-controlled certificate chain can lead the processing to easily take more than 5s to reject in testing. This amplification could form the basis for a resource exhaustion denial of service attack.&lt;/p&gt;
&lt;p&gt;This work was completed by Trail of Bits as part of the Patch The Planet project in collaboration with OpenAI. The finding was identified primarily by the Codex coding agent, and manually reviewed before submission.&lt;/p&gt;
&lt;p&gt;### Details
The core issue arises in the recursive nature of `build_chain_inner`, which does not de-duplicate against previously analyzed candidates.&lt;/p&gt;
&lt;p&gt;```python
    fn build_chain_inner(
        &amp;amp;self,
        working_cert: &amp;amp;VerificationCertificate&amp;lt;&amp;#39;chain, B&amp;gt;,
        current_depth: u8,
        working_cert_extensions: &amp;amp;Extensions&amp;lt;&amp;#39;chain&amp;gt;,
        name_chain: NameChain&amp;lt;&amp;#39;_, &amp;#39;chain&amp;gt;,
        budget: &amp;amp;mut Budget,
    ) -&amp;gt; ValidationResult&amp;lt;&amp;#39;chain, Chain&amp;lt;&amp;#39;chain, B&amp;gt;, B&amp;gt; {
        if let Some(nc) = working_cert_extensions.get_extension(&amp;amp;NAME_CONSTRAINTS_OID) {
            name_chain.evaluate_constraints(&amp;amp;nc.value()?, budget)?;
        }&lt;/p&gt;
&lt;p&gt;// Look in the store&amp;#39;s root set to see if the working cert is listed.
        // I…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: ansible@10&lt;/p&gt;
&lt;p&gt;### Summary
When resolving invalid certificate chains that include duplicate copies of self-signed certificates, the processing recursively invokes the same candidate, leading to an exponential blowup. Although the limitation that the chain depth cannot exceed a specified maximum depth prevents unbounded recursion and guarantees termination, an attacker-controlled certificate chain can lead the processing to easily take more than 5s to reject in testing. This amplification could form the basis for a resource exhaustion denial of service attack.&lt;/p&gt;
&lt;p&gt;This work was completed by Trail of Bits as part of the Patch The Planet project in collaboration with OpenAI. The finding was identified primarily by the Codex coding agent, and manually reviewed before submission.&lt;/p&gt;
&lt;p&gt;### Details
The core issue arises in the recursive nature of `build_chain_inner`, which does not de-duplicate against previously analyzed candidates.&lt;/p&gt;
&lt;p&gt;```python
    fn build_chain_inner(
        &amp;amp;self,
        working_cert: &amp;amp;VerificationCertificate&amp;lt;&amp;#39;chain, B&amp;gt;,
        current_depth: u8,
        working_cert_extensions: &amp;amp;Extensions&amp;lt;&amp;#39;chain&amp;gt;,
        name_chain: NameChain&amp;lt;&amp;#39;_, &amp;#39;chain&amp;gt;,
        budget: &amp;amp;mut Budget,
    ) -&amp;gt; ValidationResult&amp;lt;&amp;#39;chain, Chain&amp;lt;&amp;#39;chain, B&amp;gt;, B&amp;gt; {
        if let Some(nc) = working_cert_extensions.get_extension(&amp;amp;NAME_CONSTRAINTS_OID) {
            name_chain.evaluate_constraints(&amp;amp;nc.value()?, budget)?;
        }&lt;/p&gt;
&lt;p&gt;// Look in the store&amp;#39;s root set to see if the working cert is listed.
        // I…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/brew-ansible@10-cve-2026-69249</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1094 — De multiples vulnérabilités ont été découvertes dans les produits IBM. Certaines d'entre elles permettent à un attaquan…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1094</link>
      <description>certfr-2026-avi-1094</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-1094</guid>
    </item>
    <item>
      <title>Withdrawn: CLEANSTART-2026-CF86587 — Security fixes in litellm-database 1.94.3-r0</title>
      <link>https://cve.radiocsirt.org/vuln/cleanstart-2026-cf86587</link>
      <description>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; CleanStart: litellm-database&lt;/p&gt;
&lt;p&gt;Package litellm-database version 1.94.3-r0 fixes 3 vulnerabilities: CVE-2026-69247, CVE-2026-69248, CVE-2026-69249&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; CleanStart: litellm-database&lt;/p&gt;
&lt;p&gt;Package litellm-database version 1.94.3-r0 fixes 3 vulnerabilities: CVE-2026-69247, CVE-2026-69248, CVE-2026-69249&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cleanstart-2026-cf86587</guid>
    </item>
    <item>
      <title>EUVD-2026-364127</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-364127</link>
      <description>EUVD-2026-364127</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-364127</guid>
    </item>
    <item>
      <title>fkie_cve-2026-69249</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-69249</link>
      <description>&lt;p&gt;python-cryptography is a package designed to expose cryptographic primitives and recipes to Python developers. In versions 42.0.0 through 48.0.0, when resolving invalid certificate chains that include duplicate copies of self-signed certificates, the processing recursively invokes the same candidate, leading to an exponential blowup. Although the limitation that the chain depth cannot exceed a specified maximum depth prevents unbounded recursion and guarantees termination, an attacker-controlled certificate chain can lead the processing to easily take more than 5s to reject in testing. This amplification could form the basis for a resource exhaustion denial of service attack. The core issue arises in the recursive nature of build_chain_inner, which does not de-duplicate against previously analyzed candidates. As the correctness of validation is not affected, the integrity of a system cannot be compromised through this vector, only its availability. This issue is fixed in 49.0.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;python-cryptography is a package designed to expose cryptographic primitives and recipes to Python developers. In versions 42.0.0 through 48.0.0, when resolving invalid certificate chains that include duplicate copies of self-signed certificates, the processing recursively invokes the same candidate, leading to an exponential blowup. Although the limitation that the chain depth cannot exceed a specified maximum depth prevents unbounded recursion and guarantees termination, an attacker-controlled certificate chain can lead the processing to easily take more than 5s to reject in testing. This amplification could form the basis for a resource exhaustion denial of service attack. The core issue arises in the recursive nature of build_chain_inner, which does not de-duplicate against previously analyzed candidates. As the correctness of validation is not affected, the integrity of a system cannot be compromised through this vector, only its availability. This issue is fixed in 49.0.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-69249</guid>
    </item>
    <item>
      <title>GHSA-jwv3-5hgf-82ww — python-cryptography: Duplicate self-signed intermediates can cause exponential path-building</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-jwv3-5hgf-82ww</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: cryptography&lt;/p&gt;
&lt;p&gt;### Summary
When resolving invalid certificate chains that include duplicate copies of self-signed certificates, the processing recursively invokes the same candidate, leading to an exponential blowup. Although the limitation that the chain depth cannot exceed a specified maximum depth prevents unbounded recursion and guarantees termination, an attacker-controlled certificate chain can lead the processing to easily take more than 5s to reject in testing. This amplification could form the basis for a resource exhaustion denial of service attack.&lt;/p&gt;
&lt;p&gt;This work was completed by Trail of Bits as part of the Patch The Planet project in collaboration with OpenAI. The finding was identified primarily by the Codex coding agent, and manually reviewed before submission.&lt;/p&gt;
&lt;p&gt;### Details
The core issue arises in the recursive nature of `build_chain_inner`, which does not de-duplicate against previously analyzed candidates.&lt;/p&gt;
&lt;p&gt;```python
    fn build_chain_inner(
        &amp;amp;self,
        working_cert: &amp;amp;VerificationCertificate&amp;lt;&amp;#39;chain, B&amp;gt;,
        current_depth: u8,
        working_cert_extensions: &amp;amp;Extensions&amp;lt;&amp;#39;chain&amp;gt;,
        name_chain: NameChain&amp;lt;&amp;#39;_, &amp;#39;chain&amp;gt;,
        budget: &amp;amp;mut Budget,
    ) -&amp;gt; ValidationResult&amp;lt;&amp;#39;chain, Chain&amp;lt;&amp;#39;chain, B&amp;gt;, B&amp;gt; {
        if let Some(nc) = working_cert_extensions.get_extension(&amp;amp;NAME_CONSTRAINTS_OID) {
            name_chain.evaluate_constraints(&amp;amp;nc.value()?, budget)?;
        }&lt;/p&gt;
&lt;p&gt;// Look in the store&amp;#39;s root set to see if the working cert is listed.
        // I…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: cryptography&lt;/p&gt;
&lt;p&gt;### Summary
When resolving invalid certificate chains that include duplicate copies of self-signed certificates, the processing recursively invokes the same candidate, leading to an exponential blowup. Although the limitation that the chain depth cannot exceed a specified maximum depth prevents unbounded recursion and guarantees termination, an attacker-controlled certificate chain can lead the processing to easily take more than 5s to reject in testing. This amplification could form the basis for a resource exhaustion denial of service attack.&lt;/p&gt;
&lt;p&gt;This work was completed by Trail of Bits as part of the Patch The Planet project in collaboration with OpenAI. The finding was identified primarily by the Codex coding agent, and manually reviewed before submission.&lt;/p&gt;
&lt;p&gt;### Details
The core issue arises in the recursive nature of `build_chain_inner`, which does not de-duplicate against previously analyzed candidates.&lt;/p&gt;
&lt;p&gt;```python
    fn build_chain_inner(
        &amp;amp;self,
        working_cert: &amp;amp;VerificationCertificate&amp;lt;&amp;#39;chain, B&amp;gt;,
        current_depth: u8,
        working_cert_extensions: &amp;amp;Extensions&amp;lt;&amp;#39;chain&amp;gt;,
        name_chain: NameChain&amp;lt;&amp;#39;_, &amp;#39;chain&amp;gt;,
        budget: &amp;amp;mut Budget,
    ) -&amp;gt; ValidationResult&amp;lt;&amp;#39;chain, Chain&amp;lt;&amp;#39;chain, B&amp;gt;, B&amp;gt; {
        if let Some(nc) = working_cert_extensions.get_extension(&amp;amp;NAME_CONSTRAINTS_OID) {
            name_chain.evaluate_constraints(&amp;amp;nc.value()?, budget)?;
        }&lt;/p&gt;
&lt;p&gt;// Look in the store&amp;#39;s root set to see if the working cert is listed.
        // I…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-jwv3-5hgf-82ww</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-69249 — python-cryptography: Duplicate self-signed intermediates can cause exponential path-building</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-69249</link>
      <description>msrc_CVE-2026-69249</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-69249</guid>
    </item>
    <item>
      <title>OESA-2026-3457 — python-cryptography security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2026-3457</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS-SP3: python-cryptography&lt;/p&gt;
&lt;p&gt;cryptography is a package designed to expose cryptographic primitives and recipes to Python developers.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;python-cryptography is a package designed to expose cryptographic primitives and recipes to Python developers. Prior to 49.0.0, when resolving invalid certificate chains that include duplicate copies of self-signed certificates, the processing recursively invokes the same candidate, leading to an exponential blowup. Although the limitation that the chain depth cannot exceed a specified maximum depth prevents unbounded recursion and guarantees termination, an attacker-controlled certificate chain can lead the processing to easily take more than 5s to reject in testing. This amplification could form the basis for a resource exhaustion denial of service attack. The core issue arises in the recursive nature of build_chain_inner, which does not de-duplicate against previously analyzed candidates. As the correctness of validation is not affected, the integrity of a system cannot be compromised through this vector, only its availability. This issue is fixed in 49.0.0.(CVE-2026-69249)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS-SP3: python-cryptography&lt;/p&gt;
&lt;p&gt;cryptography is a package designed to expose cryptographic primitives and recipes to Python developers.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;python-cryptography is a package designed to expose cryptographic primitives and recipes to Python developers. Prior to 49.0.0, when resolving invalid certificate chains that include duplicate copies of self-signed certificates, the processing recursively invokes the same candidate, leading to an exponential blowup. Although the limitation that the chain depth cannot exceed a specified maximum depth prevents unbounded recursion and guarantees termination, an attacker-controlled certificate chain can lead the processing to easily take more than 5s to reject in testing. This amplification could form the basis for a resource exhaustion denial of service attack. The core issue arises in the recursive nature of build_chain_inner, which does not de-duplicate against previously analyzed candidates. As the correctness of validation is not affected, the integrity of a system cannot be compromised through this vector, only its availability. This issue is fixed in 49.0.0.(CVE-2026-69249)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2026-3457</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:21685-1 — Security update for python-cryptography</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:21685-1</link>
      <description>&lt;p&gt;Security update for python-cryptography&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for python-cryptography&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2026:21685-1</guid>
    </item>
    <item>
      <title>PYSEC-2026-3553 — python-cryptography: Duplicate self-signed intermediates can cause exponential path-building</title>
      <link>https://cve.radiocsirt.org/vuln/pysec-2026-3553</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: cryptography&lt;/p&gt;
&lt;p&gt;### Summary
When resolving invalid certificate chains that include duplicate copies of self-signed certificates, the processing recursively invokes the same candidate, leading to an exponential blowup. Although the limitation that the chain depth cannot exceed a specified maximum depth prevents unbounded recursion and guarantees termination, an attacker-controlled certificate chain can lead the processing to easily take more than 5s to reject in testing. This amplification could form the basis for a resource exhaustion denial of service attack.&lt;/p&gt;
&lt;p&gt;This work was completed by Trail of Bits as part of the Patch The Planet project in collaboration with OpenAI. The finding was identified primarily by the Codex coding agent, and manually reviewed before submission.&lt;/p&gt;
&lt;p&gt;### Details
The core issue arises in the recursive nature of `build_chain_inner`, which does not de-duplicate against previously analyzed candidates.&lt;/p&gt;
&lt;p&gt;```python
    fn build_chain_inner(
        &amp;amp;self,
        working_cert: &amp;amp;VerificationCertificate&amp;lt;&amp;#39;chain, B&amp;gt;,
        current_depth: u8,
        working_cert_extensions: &amp;amp;Extensions&amp;lt;&amp;#39;chain&amp;gt;,
        name_chain: NameChain&amp;lt;&amp;#39;_, &amp;#39;chain&amp;gt;,
        budget: &amp;amp;mut Budget,
    ) -&amp;gt; ValidationResult&amp;lt;&amp;#39;chain, Chain&amp;lt;&amp;#39;chain, B&amp;gt;, B&amp;gt; {
        if let Some(nc) = working_cert_extensions.get_extension(&amp;amp;NAME_CONSTRAINTS_OID) {
            name_chain.evaluate_constraints(&amp;amp;nc.value()?, budget)?;
        }&lt;/p&gt;
&lt;p&gt;// Look in the store&amp;#39;s root set to see if the working cert is listed.
        // I…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: cryptography&lt;/p&gt;
&lt;p&gt;### Summary
When resolving invalid certificate chains that include duplicate copies of self-signed certificates, the processing recursively invokes the same candidate, leading to an exponential blowup. Although the limitation that the chain depth cannot exceed a specified maximum depth prevents unbounded recursion and guarantees termination, an attacker-controlled certificate chain can lead the processing to easily take more than 5s to reject in testing. This amplification could form the basis for a resource exhaustion denial of service attack.&lt;/p&gt;
&lt;p&gt;This work was completed by Trail of Bits as part of the Patch The Planet project in collaboration with OpenAI. The finding was identified primarily by the Codex coding agent, and manually reviewed before submission.&lt;/p&gt;
&lt;p&gt;### Details
The core issue arises in the recursive nature of `build_chain_inner`, which does not de-duplicate against previously analyzed candidates.&lt;/p&gt;
&lt;p&gt;```python
    fn build_chain_inner(
        &amp;amp;self,
        working_cert: &amp;amp;VerificationCertificate&amp;lt;&amp;#39;chain, B&amp;gt;,
        current_depth: u8,
        working_cert_extensions: &amp;amp;Extensions&amp;lt;&amp;#39;chain&amp;gt;,
        name_chain: NameChain&amp;lt;&amp;#39;_, &amp;#39;chain&amp;gt;,
        budget: &amp;amp;mut Budget,
    ) -&amp;gt; ValidationResult&amp;lt;&amp;#39;chain, Chain&amp;lt;&amp;#39;chain, B&amp;gt;, B&amp;gt; {
        if let Some(nc) = working_cert_extensions.get_extension(&amp;amp;NAME_CONSTRAINTS_OID) {
            name_chain.evaluate_constraints(&amp;amp;nc.value()?, budget)?;
        }&lt;/p&gt;
&lt;p&gt;// Look in the store&amp;#39;s root set to see if the working cert is listed.
        // I…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/pysec-2026-3553</guid>
    </item>
    <item>
      <title>RHSA-2026:55543 — Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2026:55543</link>
      <description>&lt;p&gt;openssl: OpenSSL: Heap buffer overflow due to signed integer overflow in Unicode output sizing openssl: OpenSSL: Denial of Service due to heap out-of-bounds read in CMS password-based decryption openssl: OpenSSL: Heap buffer over-read in ASN.1 decoding can lead to denial of service or information disclosure. openssl: PKCS#12 Files with PBMAC1 Are Accepted with Short HMAC Keys openssl: CMS AuthEnvelopedData Processing May Accept Forged Messages openssl: Unbounded Memory Growth in the QUIC PATH_CHALLENGE Handler openssl: Double-free When Checking OCSP Stapled Response openssl: NULL pointer dereference in QUIC server initial packet handling openssl: NULL Dereference in Certificate Verification with OCSP Checking openssl: Possible NULL Dereference in Password-Based CMS Decryption openssl: NULL Pointer Dereference in CRMF EncryptedValue Decryption openssl: Multi-RecipientInfo Bleichenbacher Oracle in CMS_decrypt() and PKCS7_decrypt() openssl: Trust-Anchor Substitution via cert/issuer Typo in CMP rootCaKeyUpdate openssl: FFC-DH Peer Validation Uses Attacker-Supplied q openssl: Possible Out of Bounds Read in X509_VERIFY_PARAM_set1_email() openssl: AES-OCB IV Ignored on EVP_Cipher() Path openssl: Incorrect Tag Processing for Empty Messages in AES-GCM-SIV and AES-SIV modes openssl: Heap Use-After-Free in OpenSSL PKCS7_verify() openssl: openssl-src: OpenSSL: Memory leak leads to Denial of Service in OCSP response checking python-cryptography: python-cryptography: PKCS#7 EnvelopedData…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;openssl: OpenSSL: Heap buffer overflow due to signed integer overflow in Unicode output sizing openssl: OpenSSL: Denial of Service due to heap out-of-bounds read in CMS password-based decryption openssl: OpenSSL: Heap buffer over-read in ASN.1 decoding can lead to denial of service or information disclosure. openssl: PKCS#12 Files with PBMAC1 Are Accepted with Short HMAC Keys openssl: CMS AuthEnvelopedData Processing May Accept Forged Messages openssl: Unbounded Memory Growth in the QUIC PATH_CHALLENGE Handler openssl: Double-free When Checking OCSP Stapled Response openssl: NULL pointer dereference in QUIC server initial packet handling openssl: NULL Dereference in Certificate Verification with OCSP Checking openssl: Possible NULL Dereference in Password-Based CMS Decryption openssl: NULL Pointer Dereference in CRMF EncryptedValue Decryption openssl: Multi-RecipientInfo Bleichenbacher Oracle in CMS_decrypt() and PKCS7_decrypt() openssl: Trust-Anchor Substitution via cert/issuer Typo in CMP rootCaKeyUpdate openssl: FFC-DH Peer Validation Uses Attacker-Supplied q openssl: Possible Out of Bounds Read in X509_VERIFY_PARAM_set1_email() openssl: AES-OCB IV Ignored on EVP_Cipher() Path openssl: Incorrect Tag Processing for Empty Messages in AES-GCM-SIV and AES-SIV modes openssl: Heap Use-After-Free in OpenSSL PKCS7_verify() openssl: openssl-src: OpenSSL: Memory leak leads to Denial of Service in OCSP response checking python-cryptography: python-cryptography: PKCS#7 EnvelopedData…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2026:55543</guid>
    </item>
    <item>
      <title>RLSA-2026:64774 — Important: python3.14-cryptography security update</title>
      <link>https://cve.radiocsirt.org/vuln/rlsa-2026:64774</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Rocky Linux:9: python3.14-cryptography&lt;/p&gt;
&lt;p&gt;Python is an interpreted, interactive, object-oriented programming language, which includes modules, classes, exceptions, very high level dynamic data types and dynamic typing. Python supports interfaces to many system calls and libraries, as well as to various windowing systems.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* python-cryptography: python-cryptography: Duplicate self-signed intermediates can cause exponential path-building (CVE-2026-69249)&lt;/p&gt;
&lt;p&gt;* python-cryptography: python-cryptography: python-cryptography verifier accepts wildcard DNS names allowing escape from permittedSubtrees (CVE-2026-69248)&lt;/p&gt;
&lt;p&gt;For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Rocky Linux:9: python3.14-cryptography&lt;/p&gt;
&lt;p&gt;Python is an interpreted, interactive, object-oriented programming language, which includes modules, classes, exceptions, very high level dynamic data types and dynamic typing. Python supports interfaces to many system calls and libraries, as well as to various windowing systems.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* python-cryptography: python-cryptography: Duplicate self-signed intermediates can cause exponential path-building (CVE-2026-69249)&lt;/p&gt;
&lt;p&gt;* python-cryptography: python-cryptography: python-cryptography verifier accepts wildcard DNS names allowing escape from permittedSubtrees (CVE-2026-69248)&lt;/p&gt;
&lt;p&gt;For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rlsa-2026:64774</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:23196-1 — Security update for python-cryptography</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2026:23196-1</link>
      <description>&lt;p&gt;Security update for python-cryptography&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for python-cryptography&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2026:23196-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-69249</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-69249</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:26.04:LTS: python-cryptography&lt;/p&gt;
&lt;p&gt;python-cryptography is a package designed to expose cryptographic primitives and recipes to Python developers. In versions 42.0.0 through 48.0.0, when resolving invalid certificate chains that include duplicate copies of self-signed certificates, the processing recursively invokes the same candidate, leading to an exponential blowup. Although the limitation that the chain depth cannot exceed a specified maximum depth prevents unbounded recursion and guarantees termination, an attacker-controlled certificate chain can lead the processing to easily take more than 5s to reject in testing. This amplification could form the basis for a resource exhaustion denial of service attack. The core issue arises in the recursive nature of build_chain_inner, which does not de-duplicate against previously analyzed candidates. As the correctness of validation is not affected, the integrity of a system cannot be compromised through this vector, only its availability. This issue is fixed in 49.0.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:26.04:LTS: python-cryptography&lt;/p&gt;
&lt;p&gt;python-cryptography is a package designed to expose cryptographic primitives and recipes to Python developers. In versions 42.0.0 through 48.0.0, when resolving invalid certificate chains that include duplicate copies of self-signed certificates, the processing recursively invokes the same candidate, leading to an exponential blowup. Although the limitation that the chain depth cannot exceed a specified maximum depth prevents unbounded recursion and guarantees termination, an attacker-controlled certificate chain can lead the processing to easily take more than 5s to reject in testing. This amplification could form the basis for a resource exhaustion denial of service attack. The core issue arises in the recursive nature of build_chain_inner, which does not de-duplicate against previously analyzed candidates. As the correctness of validation is not affected, the integrity of a system cannot be compromised through this vector, only its availability. This issue is fixed in 49.0.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-69249</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-3214 — Red Hat Enterprise Linux (python-cryptography): Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3214</link>
      <description>&lt;p&gt;Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Red Hat Enterprise Linux ausnutzen, um Sicherheitsvorkehrungen zu umgehen oder um einen Denial-of-Service-Zustand herbeizuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Red Hat Enterprise Linux ausnutzen, um Sicherheitsvorkehrungen zu umgehen oder um einen Denial-of-Service-Zustand herbeizuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3214</guid>
    </item>
  </channel>
</rss>
