<?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, 13 Oct 2026 05:54:49 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-218920</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-218920</link>
      <description>EUVD-2026-218920</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-218920</guid>
    </item>
    <item>
      <title>fkie_cve-2023-22481</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-22481</link>
      <description>&lt;p&gt;FreshRSS is a self-hosted RSS feed aggregator. When using the greader API, the provided password is logged in clear in `users/_/log_api.txt` in the case where the authentication fails. The issues occurs in `authorizationToUser()` in `greader.php`. If there is an issue with the request or the credentials, `unauthorized()` or `badRequest()` is called. Both these functions are printing the return of `debugInfo()` in the logs.  `debugInfo()` will return the content of the request. By default, this will be saved in `users/_/log_api.txt` and if the const `COPY_LOG_TO_SYSLOG` is true, in syslogs as well. Exploiting this issue requires having access to logs produced by FreshRSS. Using the information from the logs, a malicious individual could get users&amp;#39; API keys (would be displayed if the users fills in a bad username) or passwords.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;FreshRSS is a self-hosted RSS feed aggregator. When using the greader API, the provided password is logged in clear in `users/_/log_api.txt` in the case where the authentication fails. The issues occurs in `authorizationToUser()` in `greader.php`. If there is an issue with the request or the credentials, `unauthorized()` or `badRequest()` is called. Both these functions are printing the return of `debugInfo()` in the logs.  `debugInfo()` will return the content of the request. By default, this will be saved in `users/_/log_api.txt` and if the const `COPY_LOG_TO_SYSLOG` is true, in syslogs as well. Exploiting this issue requires having access to logs produced by FreshRSS. Using the information from the logs, a malicious individual could get users&amp;#39; API keys (would be displayed if the users fills in a bad username) or passwords.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2023-22481</guid>
    </item>
    <item>
      <title>gsd-2023-22481</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2023-22481</link>
      <description>gsd-2023-22481</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2023-22481</guid>
    </item>
  </channel>
</rss>
