<?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>Node-Forge (&lt; 1.4.1) - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/products/node-forge--1.4.1/</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>Thu, 29 Oct 2026 21:10:37 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/products/node-forge--1.4.1/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>node-forge: Certificate validation bypass via deprecated extensions (CVE-2026-119190)</title><link>https://feed.craftedsignal.io/briefs/2026-10-node-forge-cert-bypass/</link><pubDate>Thu, 29 Oct 2026 21:10:37 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-10-node-forge-cert-bypass/</guid><description>Prior to version 1.4.1, node-forge incorrectly parses deprecated certificate extensions, potentially allowing a certificate to be accepted as a CA and enabling impersonation.</description><content:encoded>&lt;p>node-forge versions prior to 1.4.1 parsed deprecated extension OIDs 2.5.29.10 and 2.5.29.13 as basicConstraints, with pki.verifyCertificateChain() prioritizing the first extension encountered. If a trusted CA issues a certificate containing these attacker-supplied extensions, the certificate may be accepted as a CA. This allows for server or client impersonation. If the CA includes a keyUsage extension without keyCertSign, the chain is rejected. This issue is addressed in version 1.4.1.&lt;/p>
</content:encoded><category domain="severity">high</category><category domain="type">advisory</category></item><item><title>Digital Bazaar node-forge: ReDoS in pem.decode() (CVE-2026-118779)</title><link>https://feed.craftedsignal.io/briefs/2026-10-node-forge-redos/</link><pubDate>Thu, 29 Oct 2026 20:40:45 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-10-node-forge-redos/</guid><description>Digital Bazaar node-forge versions prior to 1.4.1 are vulnerable to a Regular Expression Denial of Service (ReDoS) in the pem.decode() function, allowing unauthenticated attackers to cause high CPU usage via malformed PEM input.</description><content:encoded><![CDATA[<p>The node-forge library, a native JavaScript implementation of TLS, contains a vulnerability in its <code>pem.decode()</code> function within <code>lib/pem.js</code>. The library uses polynomial-time regular expressions to process PEM input, including the search for matching END lines and the parsing of encapsulated headers. An unauthenticated attacker can supply crafted, malformed PEM input to any high-level parser relying on this function, triggering catastrophic backtracking that leads to excessive CPU consumption and denial of service. This vulnerability is identified as CVE-2026-118779.</p>
<h2 id="impact">Impact</h2>
<p>Successful exploitation results in high CPU utilization, potentially leading to a denial-of-service condition for applications relying on the node-forge library to process user-supplied PEM files or certificates.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade the node-forge library to version 1.4.1 or later immediately.</li>
<li>Inventory applications within the environment that utilize the node-forge library for certificate or PEM parsing.</li>
<li>Review input validation controls for services that ingest PEM-encoded data to ensure length and complexity constraints are enforced before processing by the library.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category></item></channel></rss>