<?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://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-28T23:13:32.990017+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" 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://vulnerability.circl.lu/vuln/cleanstart-2026-fv05780</id>
    <title>Withdrawn: CLEANSTART-2026-FV05780 — Security fixes in langfuse 3.213.0-r1</title>
    <updated>2026-09-28T23:13:33.000990+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Withdrawn by the publisher.</strong></p>
<p><strong>Affected:</strong> CleanStart: langfuse</p>
<p>Package langfuse version 3.213.0-r1 fixes 24 vulnerabilities: CVE-2026-59895, CVE-2026-59896, CVE-2026-59897, CVE-2026-69207, CVE-2026-71848...</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cleanstart-2026-fv05780"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/fkie_cve-2026-64643</id>
    <title>fkie_cve-2026-64643</title>
    <updated>2026-09-28T23:13:33.001071+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Next.js is a React framework for building full-stack web applications. In versions 12.0.0 through 15.5.20 and 16.0.0 through 16.2.10, Next.js applications using App Router, Server Actions (use server) or use cache endpoints can be disclosed bypassing any authentication on the pages where these endpoints are usually used. Server Action IDs can be disclosed to unauthenticated users via publicly served client artifacts (for example, static chunks containing action references). Affected users are applications using App Router and Server Actions. By itself, this disclosure is typically a recon/enumeration primitive; however, it can increase risk when combined with other weaknesses. This issue has been fixed in versions 15.5.21 and 16.2.11.</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/fkie_cve-2026-64643"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-955p-x3mx-jcvp</id>
    <title>GHSA-955p-x3mx-jcvp — Next.js: Unauthenticated disclosure of internal Server Function endpoints</title>
    <updated>2026-09-28T23:13:33.001131+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: next</p>
<p>## Impact</p>
<p>In Next.js applications using App Router, Server Actions (`use server`) or `use cache` endpoints can be disclosed bypassing any authentication on the pages where these endpoints are usually used.</p>
<p>Server Action IDs can be disclosed to unauthenticated users via publicly served client artifacts (for example, static chunks containing action references).</p>
<p>Affected users are applications using App Router + Server Actions.</p>
<p>By itself, this disclosure is typically a recon/enumeration primitive; however, it can increase risk when combined with other weaknesses.
 
## Workarounds</p>
<p>Never assume any authentication claims at the `use cache` or `use server` boundary. Always authenticate within the boundary.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-955p-x3mx-jcvp"/>
  </entry>
</feed>
