<?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>Tue, 17 Nov 2026 05:13:57 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-395613</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-395613</link>
      <description>EUVD-2026-395613</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-395613</guid>
    </item>
    <item>
      <title>fkie_cve-2026-118774</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-118774</link>
      <description>&lt;p&gt;Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to 1.4.1, the affected implementation used certificate.verify(child), _verifySignature(), lib/x509.js to process the relevant input or security decision. node-forge selected RSA padding and RSASSA-PSS parameters from the issuer certificate rather than the child certificate being verified. A child labeled as RSASSA-PSS could therefore be accepted with a PKCS#1 v1.5 signature when the issuer used PKCS#1 v1.5. The signature still had to be produced with the trusted issuer&amp;#39;s private key, so this did not permit certificate identity forgery, but it could bypass policies that require a declared signature scheme. This issue is fixed in version 1.4.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to 1.4.1, the affected implementation used certificate.verify(child), _verifySignature(), lib/x509.js to process the relevant input or security decision. node-forge selected RSA padding and RSASSA-PSS parameters from the issuer certificate rather than the child certificate being verified. A child labeled as RSASSA-PSS could therefore be accepted with a PKCS#1 v1.5 signature when the issuer used PKCS#1 v1.5. The signature still had to be produced with the trusted issuer&amp;#39;s private key, so this did not permit certificate identity forgery, but it could bypass policies that require a declared signature scheme. This issue is fixed in version 1.4.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-118774</guid>
    </item>
    <item>
      <title>GHSA-9wg5-mj3p-v49q — Forge: Certificate signature verified with the issuer's RSA signature scheme</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-9wg5-mj3p-v49q</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: node-forge&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;When verifying a certificate, node-forge chose the RSA padding scheme (PKCS#1 v1.5 or RSASSA-PSS) and PSS parameters from the issuer certificate&amp;#39;s own signature algorithm instead of the certificate being verified. A certificate labeled as signed with RSASSA-PSS could pass `verifyCertificateChain()` with a PKCS#1 v1.5 signature. Fixed in node-forge 1.4.1.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;`certificate.verify(child)` in `lib/x509.js` hashes the child&amp;#39;s TBSCertificate with the digest of the child&amp;#39;s signature algorithm, then calls `_verifySignature()` with the issuer certificate. `_verifySignature()` selected the padding scheme from that certificate&amp;#39;s `signatureOid` and `signatureParameters`, so the child was verified with the issuer&amp;#39;s own scheme rather than the one the child declares.&lt;/p&gt;
&lt;p&gt;As a result, a child certificate whose signature algorithm says RSASSA-PSS was accepted with a PKCS#1 v1.5 signature when the issuer itself was signed with PKCS#1 v1.5. The outer `signatureAlgorithm` field of a certificate is not covered by the signature, so an existing PKCS#1 v1.5 (SHA-256) certificate can be relabeled as RSASSA-PSS and still pass verification. The signature itself must still be made with the issuer&amp;#39;s private key over the certificate&amp;#39;s contents; no certificate can be forged.&lt;/p&gt;
&lt;p&gt;The same cause made correctly signed chains fail: a PKCS#1 v1.5 certificate issued by an RSASSA-PSS-signed certificate, or the reverse, was rejected.&lt;/p&gt;
&lt;p&gt;The fix verifies with the child certificate&amp;#39;s signature scheme…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: node-forge&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;When verifying a certificate, node-forge chose the RSA padding scheme (PKCS#1 v1.5 or RSASSA-PSS) and PSS parameters from the issuer certificate&amp;#39;s own signature algorithm instead of the certificate being verified. A certificate labeled as signed with RSASSA-PSS could pass `verifyCertificateChain()` with a PKCS#1 v1.5 signature. Fixed in node-forge 1.4.1.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;`certificate.verify(child)` in `lib/x509.js` hashes the child&amp;#39;s TBSCertificate with the digest of the child&amp;#39;s signature algorithm, then calls `_verifySignature()` with the issuer certificate. `_verifySignature()` selected the padding scheme from that certificate&amp;#39;s `signatureOid` and `signatureParameters`, so the child was verified with the issuer&amp;#39;s own scheme rather than the one the child declares.&lt;/p&gt;
&lt;p&gt;As a result, a child certificate whose signature algorithm says RSASSA-PSS was accepted with a PKCS#1 v1.5 signature when the issuer itself was signed with PKCS#1 v1.5. The outer `signatureAlgorithm` field of a certificate is not covered by the signature, so an existing PKCS#1 v1.5 (SHA-256) certificate can be relabeled as RSASSA-PSS and still pass verification. The signature itself must still be made with the issuer&amp;#39;s private key over the certificate&amp;#39;s contents; no certificate can be forged.&lt;/p&gt;
&lt;p&gt;The same cause made correctly signed chains fail: a PKCS#1 v1.5 certificate issued by an RSASSA-PSS-signed certificate, or the reverse, was rejected.&lt;/p&gt;
&lt;p&gt;The fix verifies with the child certificate&amp;#39;s signature scheme…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-9wg5-mj3p-v49q</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-118774 — Forge: Certificate signature verified with the issuer's RSA signature scheme</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-118774</link>
      <description>msrc_CVE-2026-118774</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-118774</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-118774</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-118774</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:20.04:LTS: node-node-forge, Ubuntu:22.04:LTS: node-node-forge&lt;/p&gt;
&lt;p&gt;Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to 1.4.1, the affected implementation used certificate.verify(child), _verifySignature(), lib/x509.js to process the relevant input or security decision. node-forge selected RSA padding and RSASSA-PSS parameters from the issuer certificate rather than the child certificate being verified. A child labeled as RSASSA-PSS could therefore be accepted with a PKCS#1 v1.5 signature when the issuer used PKCS#1 v1.5. The signature still had to be produced with the trusted issuer&amp;#39;s private key, so this did not permit certificate identity forgery, but it could bypass policies that require a declared signature scheme. This issue is fixed in version 1.4.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:20.04:LTS: node-node-forge, Ubuntu:22.04:LTS: node-node-forge&lt;/p&gt;
&lt;p&gt;Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to 1.4.1, the affected implementation used certificate.verify(child), _verifySignature(), lib/x509.js to process the relevant input or security decision. node-forge selected RSA padding and RSASSA-PSS parameters from the issuer certificate rather than the child certificate being verified. A child labeled as RSASSA-PSS could therefore be accepted with a PKCS#1 v1.5 signature when the issuer used PKCS#1 v1.5. The signature still had to be produced with the trusted issuer&amp;#39;s private key, so this did not permit certificate identity forgery, but it could bypass policies that require a declared signature scheme. This issue is fixed in version 1.4.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-118774</guid>
    </item>
  </channel>
</rss>
