<?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>Fri, 09 Oct 2026 06:27:18 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-216435</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-216435</link>
      <description>EUVD-2026-216435</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-216435</guid>
    </item>
    <item>
      <title>fkie_cve-2023-30846</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-30846</link>
      <description>&lt;p&gt;typed-rest-client is a library for Node Rest and Http Clients with typings for use with TypeScript. Users of the typed-rest-client library version 1.7.3 or lower are vulnerable to leak authentication data to 3rd parties. The flow of the vulnerability is as follows: First, send any request with `BasicCredentialHandler`, `BearerCredentialHandler` or `PersonalAccessTokenCredentialHandler`. Second, the target host may return a redirection (3xx), with a link to a second host. Third, the next request will use the credentials to authenticate with the second host, by setting the `Authorization` header. The expected behavior is that the next request will *NOT* set the `Authorization` header. The problem was fixed in version 1.8.0. There are no known workarounds.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;typed-rest-client is a library for Node Rest and Http Clients with typings for use with TypeScript. Users of the typed-rest-client library version 1.7.3 or lower are vulnerable to leak authentication data to 3rd parties. The flow of the vulnerability is as follows: First, send any request with `BasicCredentialHandler`, `BearerCredentialHandler` or `PersonalAccessTokenCredentialHandler`. Second, the target host may return a redirection (3xx), with a link to a second host. Third, the next request will use the credentials to authenticate with the second host, by setting the `Authorization` header. The expected behavior is that the next request will *NOT* set the `Authorization` header. The problem was fixed in version 1.8.0. There are no known workarounds.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2023-30846</guid>
    </item>
    <item>
      <title>GHSA-558p-m34m-vpmq — Potential leak of authentication data to 3rd parties</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-558p-m34m-vpmq</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: typed-rest-client&lt;/p&gt;
&lt;p&gt;### Impact
Users of typed-rest-client library version 1.7.3 or lower are vulnerable to leak authentication data to 3rd parties.&lt;/p&gt;
&lt;p&gt;The flow of the vulnerability is as follows:&lt;/p&gt;
&lt;p&gt;1. Send any request with `BasicCredentialHandler`, `BearerCredentialHandler` or `PersonalAccessTokenCredentialHandler` 
2. The target host may return a redirection (3xx), with a link to a second host.
3. The next request will use the credentials to authenticate with the second host, by setting the `Authorization` header.&lt;/p&gt;
&lt;p&gt;The expected behavior is that the next request will *NOT* set the `Authorization` header.&lt;/p&gt;
&lt;p&gt;### Patches
The problem was fixed on April 1st 2020.&lt;/p&gt;
&lt;p&gt;### Workarounds
There is no workaround.&lt;/p&gt;
&lt;p&gt;### References
This is similar to the following issues in nature:
1. [HTTP authentication leak in redirects](https://curl.haxx.se/docs/CVE-2018-1000007.html) - I used the same solution as CURL did.
2. [CVE-2018-1000007](https://nvd.nist.gov/vuln/detail/CVE-2018-1000007).&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: typed-rest-client&lt;/p&gt;
&lt;p&gt;### Impact
Users of typed-rest-client library version 1.7.3 or lower are vulnerable to leak authentication data to 3rd parties.&lt;/p&gt;
&lt;p&gt;The flow of the vulnerability is as follows:&lt;/p&gt;
&lt;p&gt;1. Send any request with `BasicCredentialHandler`, `BearerCredentialHandler` or `PersonalAccessTokenCredentialHandler` 
2. The target host may return a redirection (3xx), with a link to a second host.
3. The next request will use the credentials to authenticate with the second host, by setting the `Authorization` header.&lt;/p&gt;
&lt;p&gt;The expected behavior is that the next request will *NOT* set the `Authorization` header.&lt;/p&gt;
&lt;p&gt;### Patches
The problem was fixed on April 1st 2020.&lt;/p&gt;
&lt;p&gt;### Workarounds
There is no workaround.&lt;/p&gt;
&lt;p&gt;### References
This is similar to the following issues in nature:
1. [HTTP authentication leak in redirects](https://curl.haxx.se/docs/CVE-2018-1000007.html) - I used the same solution as CURL did.
2. [CVE-2018-1000007](https://nvd.nist.gov/vuln/detail/CVE-2018-1000007).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-558p-m34m-vpmq</guid>
    </item>
    <item>
      <title>gsd-2023-30846</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2023-30846</link>
      <description>gsd-2023-30846</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2023-30846</guid>
    </item>
  </channel>
</rss>
