<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-02T12:26:08.006711+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cve-2025-15599</id>
    <title>CVE-2025-15599 — DOMPurify XSS via Textarea Rawtext Bypass in SAFE_FOR_XML</title>
    <updated>2026-10-02T12:26:08.063261+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> cure53 DOMPurify</p>
<p>DOMPurify 3.1.3 through 3.2.6 and 2.5.3 through 2.5.8 contain a cross-site scripting vulnerability that allows attackers to bypass attribute sanitization by exploiting missing textarea rawtext element validation in the SAFE_FOR_XML regex. Attackers can include closing rawtext tags like &lt;/textarea&gt; in attribute values to break out of rawtext contexts and execute JavaScript when sanitized output is placed inside rawtext elements. The 3.x branch was fixed in 3.2.7; the 2.x branch was never patched.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2025-15599"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-2328-f5f3-gj25</id>
    <title>GHSA-2328-f5f3-gj25 — Forge has a basicConstraints bypass in its certificate chain verification (RFC 5280 violation)</title>
    <updated>2026-10-02T12:26:08.063332+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: node-forge</p>
<p>## Summary</p>
<p>`pki.verifyCertificateChain()` does not enforce RFC 5280 basicConstraints requirements when an intermediate certificate lacks both the `basicConstraints` and `keyUsage` extensions. This allows any leaf certificate (without these extensions) to act as a CA and sign other certificates, which node-forge will accept as valid.</p>
<p>## Technical Details</p>
<p>In `lib/x509.js`, the `verifyCertificateChain()` function (around lines 3147-3199) has two conditional checks for CA authorization:</p>
<p>1. The `keyUsage` check (which includes a sub-check requiring `basicConstraints` to be present) is gated on `keyUsageExt !== null`
2. The `basicConstraints.cA` check is gated on `bcExt !== null`</p>
<p>When a certificate has **neither** extension, both checks are skipped entirely. The certificate passes all CA validation and is accepted as a valid intermediate CA.</p>
<p>**RFC 5280 Section 6.1.4 step (k) requires:**
&gt; "If certificate i is a version 3 certificate, verify that the basicConstraints extension is present and that cA is set to TRUE."</p>
<p>The absence of `basicConstraints` should result in rejection, not acceptance.</p>
<p>## Proof of Concept</p>
<p>```javascript
const forge = require('node-forge');
const pki = forge.pki;</p>
<p>function generateKeyPair() {
  return pki.rsa.generateKeyPair({ bits: 2048, e: 0x10001 });
}</p>
<p>console.log('=== node-forge basicConstraints Bypass PoC ===\n');</p>
<p>// 1. Create a legitimate Root CA (self-signed, with basicConstraints cA=true)
const rootKeys = generateKeyPair();
const rootCert =…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-2328-f5f3-gj25"/>
  </entry>
</feed>
