<?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>Mon, 19 Oct 2026 11:56:12 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-46904</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-46904</link>
      <description>EUVD-2026-46904</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-46904</guid>
    </item>
    <item>
      <title>fkie_cve-2020-28086</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2020-28086</link>
      <description>&lt;p&gt;pass through 1.7.3 has a possibility of using a password for an unintended resource. For exploitation to occur, the user must do a git pull, decrypt a password, and log into a remote service with the password. If an attacker controls the central Git server or one of the other members&amp;#39; machines, and also controls one of the services already in the password store, they can rename one of the password files in the Git repository to something else: pass doesn&amp;#39;t correctly verify that the content of a file matches the filename, so a user might be tricked into decrypting the wrong password and sending that to a service that the attacker controls. NOTE: for environments in which this threat model is of concern, signing commits can be a solution.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;pass through 1.7.3 has a possibility of using a password for an unintended resource. For exploitation to occur, the user must do a git pull, decrypt a password, and log into a remote service with the password. If an attacker controls the central Git server or one of the other members&amp;#39; machines, and also controls one of the services already in the password store, they can rename one of the password files in the Git repository to something else: pass doesn&amp;#39;t correctly verify that the content of a file matches the filename, so a user might be tricked into decrypting the wrong password and sending that to a service that the attacker controls. NOTE: for environments in which this threat model is of concern, signing commits can be a solution.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2020-28086</guid>
    </item>
    <item>
      <title>GHSA-phjf-vhjh-qv5p</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-phjf-vhjh-qv5p</link>
      <description>&lt;p&gt;pass through 1.7.3 has a possibility of using a password for an unintended resource. For exploitation to occur, the user must do a git pull, decrypt a password, and log into a remote service with the password. If an attacker controls the central Git server or one of the other members&amp;#39; machines, and also controls one of the services already in the password store, they can rename one of the password files in the Git repository to something else: pass doesn&amp;#39;t correctly verify that the content of a file matches the filename, so a user might be tricked into decrypting the wrong password and sending that to a service that the attacker controls. NOTE: for environments in which this threat model is of concern, signing commits can be a solution.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;pass through 1.7.3 has a possibility of using a password for an unintended resource. For exploitation to occur, the user must do a git pull, decrypt a password, and log into a remote service with the password. If an attacker controls the central Git server or one of the other members&amp;#39; machines, and also controls one of the services already in the password store, they can rename one of the password files in the Git repository to something else: pass doesn&amp;#39;t correctly verify that the content of a file matches the filename, so a user might be tricked into decrypting the wrong password and sending that to a service that the attacker controls. NOTE: for environments in which this threat model is of concern, signing commits can be a solution.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-phjf-vhjh-qv5p</guid>
    </item>
    <item>
      <title>gsd-2020-28086</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2020-28086</link>
      <description>gsd-2020-28086</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2020-28086</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2020-28086</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2020-28086</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: password-store, Ubuntu:18.04:LTS: password-store, Ubuntu:20.04:LTS: password-store, Ubuntu:22.04:LTS: password-store, Ubuntu:24.04:LTS: password-store, Ubuntu:25.10: password-store, Ubuntu:26.10: password-store, Ubuntu:26.04:LTS: password-store&lt;/p&gt;
&lt;p&gt;pass through 1.7.3 has a possibility of using a password for an unintended resource. For exploitation to occur, the user must do a git pull, decrypt a password, and log into a remote service with the password. If an attacker controls the central Git server or one of the other members&amp;#39; machines, and also controls one of the services already in the password store, they can rename one of the password files in the Git repository to something else: pass doesn&amp;#39;t correctly verify that the content of a file matches the filename, so a user might be tricked into decrypting the wrong password and sending that to a service that the attacker controls. NOTE: for environments in which this threat model is of concern, signing commits can be a solution.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: password-store, Ubuntu:18.04:LTS: password-store, Ubuntu:20.04:LTS: password-store, Ubuntu:22.04:LTS: password-store, Ubuntu:24.04:LTS: password-store, Ubuntu:25.10: password-store, Ubuntu:26.10: password-store, Ubuntu:26.04:LTS: password-store&lt;/p&gt;
&lt;p&gt;pass through 1.7.3 has a possibility of using a password for an unintended resource. For exploitation to occur, the user must do a git pull, decrypt a password, and log into a remote service with the password. If an attacker controls the central Git server or one of the other members&amp;#39; machines, and also controls one of the services already in the password store, they can rename one of the password files in the Git repository to something else: pass doesn&amp;#39;t correctly verify that the content of a file matches the filename, so a user might be tricked into decrypting the wrong password and sending that to a service that the attacker controls. NOTE: for environments in which this threat model is of concern, signing commits can be a solution.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2020-28086</guid>
    </item>
  </channel>
</rss>
