<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:webfeeds="http://webfeeds.org/rss/1.0"><channel><title>Cpe:2.3:a:apache:qpid_proton:*:*:*:*:*:*:*:* - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/cpes/cpe2.3aapacheqpid_proton/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Wed, 28 Oct 2026 22:24:34 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/cpes/cpe2.3aapacheqpid_proton/feed.xml" rel="self" type="application/rss+xml"/><image><url>https://feed.craftedsignal.io/favicon-32x32.png</url><title>CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/</link><width>32</width><height>32</height></image><webfeeds:icon>https://feed.craftedsignal.io/favicon.svg</webfeeds:icon><item><title>Apache Qpid Proton C: Stack buffer overflow read in TLS certificate validation (CVE-2026-115942)</title><link>https://feed.craftedsignal.io/briefs/2026-10-apache-qpid-proton-c-buffer-overflow/</link><pubDate>Wed, 28 Oct 2026 22:24:34 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-10-apache-qpid-proton-c-buffer-overflow/</guid><description>Apache Qpid Proton C versions through 0.40.0 contain a stack buffer overflow read vulnerability triggered by misconfigured wildcard TLS certificates.</description><content:encoded>&lt;p>Apache Qpid Proton C versions through 0.40.0 are affected by a stack buffer overflow read caused by the verification of non-compliant wildcard TLS certificates. The issue does not affect certificates issued to the RFC9525 standard. Version 0.41.1 has been released to fix this issue by only accepting certificates that comply with the RFC9525 standard.&lt;/p>
</content:encoded><category domain="severity">high</category><category domain="type">advisory</category></item></channel></rss>