<?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-04T09:31:49.757018+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/cnvd-2026-19025</id>
    <title>cnvd-2026-19025</title>
    <updated>2026-10-04T09:31:49.761331+00:00</updated>
    <content>cnvd-2026-19025</content>
    <link href="https://cve.radiocsirt.org/vuln/cnvd-2026-19025"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-292885</id>
    <title>EUVD-2026-292885</title>
    <updated>2026-10-04T09:31:49.761365+00:00</updated>
    <content>EUVD-2026-292885</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-292885"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-41278</id>
    <title>fkie_cve-2026-41278</title>
    <updated>2026-10-04T09:31:49.761380+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Flowise is a drag &amp; drop user interface to build a customized large language model flow. Prior to 3.1.0, the GET /api/v1/public-chatflows/:id endpoint returns the full chatflow object without sanitization for public chatflows. Docker validation revealed this is worse than initially assessed: the sanitizeFlowDataForPublicEndpoint function does NOT exist in the released v3.0.13 Docker image. Both public-chatflows AND public-chatbotConfig return completely raw flowData including credential IDs, plaintext API keys, and password-type fields. This vulnerability is fixed in 3.1.0.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-41278"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-w47f-j8rh-wx87</id>
    <title>GHSA-w47f-j8rh-wx87 — Flowise: Public chatflow endpoints return unsanitized flowData including plaintext API keys, passwords, and credential…</title>
    <updated>2026-10-04T09:31:49.761411+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: flowise</p>
<p>### Summary</p>
<p>The `GET /api/v1/public-chatflows/:id` endpoint returns the full chatflow object **without sanitization** for public chatflows. Docker validation revealed this is worse than initially assessed: the `sanitizeFlowDataForPublicEndpoint` function does NOT exist in the released v3.0.13 Docker image. Both `public-chatflows` AND `public-chatbotConfig` return completely raw flowData including credential IDs, plaintext API keys, and password-type fields.</p>
<p>### Root Cause</p>
<p>```typescript
// packages/server/src/controllers/chatflows/index.ts:218-220
const chatflow = await chatflowsService.getChatflowById(req.params.id)
if (!chatflow) return res.status(StatusCodes.NOT_FOUND).json(...)
if (chatflow.isPublic) return res.status(StatusCodes.OK).json(chatflow) // ← NO sanitization!
```</p>
<p>### Docker Validation (v3.0.13)</p>
<p>Created public chatflow with credential IDs and passwords in flowData:
```json
{
  "flowData": "{\"nodes\":[{\"data\":{\"credential\":\"e92a39bf-...\",\"inputs\":{\"password\":\"sk-supersecretkey123\",\"apiKey\":\"should-not-leak\"}}}]}"
}
```</p>
<p>The `sanitizeFlowDataForPublicEndpoint` function only exists in unreleased HEAD, and even there, only `public-chatbotConfig` calls it — `public-chatflows` never does.</p>
<p>### Impact</p>
<p>- **Credential IDs** leaked — enables OAuth2 token theft chain (Finding 1)
- **Plaintext API keys and passwords** leaked — direct third-party account compromise
- **Node configurations** leaked — reveals internal architecture and endpoint URLs
- Bot…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-w47f-j8rh-wx87"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1145</id>
    <title>WID-SEC-W-2026-1145 — Flowise: Mehrere Schwachstellen</title>
    <updated>2026-10-04T09:31:49.761462+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Ein Angreifer kann mehrere Schwachstellen in Flowise ausnutzen, um beliebigen Programmcode auszuführen, um Sicherheitsvorkehrungen zu umgehen, um Informationen offenzulegen, und um Dateien zu manipulieren.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1145"/>
  </entry>
</feed>
