<?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-09T12:03:59.081127+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/euvd-2026-273801</id>
    <title>EUVD-2026-273801</title>
    <updated>2026-10-09T12:03:59.127040+00:00</updated>
    <content>EUVD-2026-273801</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-273801"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2025-69971</id>
    <title>fkie_cve-2025-69971</title>
    <updated>2026-10-09T12:03:59.127075+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>FUXA v1.2.7 contains a hard-coded credential vulnerability in server/api/jwt-helper.js. The application uses a hard-coded secret key to sign and verify JWT Tokens. This allows remote attackers to forge valid admin tokens and bypass authentication to gain full administrative access.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2025-69971"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-c8m8-3jcr-6rj5</id>
    <title>GHSA-c8m8-3jcr-6rj5 — FUXA has a hardcoded fallback JWT signing secret</title>
    <updated>2026-10-09T12:03:59.127107+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: @frangoteam/fuxa</p>
<p>FUXA used a static fallback JWT signing secret (`frangoteam751`) when no `secretCode` was configured.</p>
<p>If authentication was enabled without explicitly setting a custom secret, an attacker who knew the default value could forge valid JWT tokens and bypass authentication.</p>
<p>This issue has been addressed in version 1.3.0 by removing the static fallback and generating a secure random secret when no `secretCode` is provided.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-c8m8-3jcr-6rj5"/>
  </entry>
</feed>
