<?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>Sat, 10 Oct 2026 19:53:49 +0000</lastBuildDate>
    <item>
      <title>cnvd-2018-02833</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2018-02833</link>
      <description>cnvd-2018-02833</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2018-02833</guid>
    </item>
    <item>
      <title>EUVD-2026-80897</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-80897</link>
      <description>EUVD-2026-80897</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-80897</guid>
    </item>
    <item>
      <title>fkie_cve-2017-1000387</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2017-1000387</link>
      <description>&lt;p&gt;Jenkins Build-Publisher plugin version 1.21 and earlier stores credentials to other Jenkins instances in the file hudson.plugins.build_publisher.BuildPublisher.xml in the Jenkins master home directory. These credentials were stored unencrypted, allowing anyone with local file system access to access them. Additionally, the credentials were also transmitted in plain text as part of the configuration form. This could result in exposure of the credentials through browser extensions, cross-site scripting vulnerabilities, and similar situations.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Jenkins Build-Publisher plugin version 1.21 and earlier stores credentials to other Jenkins instances in the file hudson.plugins.build_publisher.BuildPublisher.xml in the Jenkins master home directory. These credentials were stored unencrypted, allowing anyone with local file system access to access them. Additionally, the credentials were also transmitted in plain text as part of the configuration form. This could result in exposure of the credentials through browser extensions, cross-site scripting vulnerabilities, and similar situations.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2017-1000387</guid>
    </item>
    <item>
      <title>GHSA-m3wv-fr8v-fmh7 — Jenkins Build-Publisher plugin has Insufficiently Protected Credentials</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-m3wv-fr8v-fmh7</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: org.jenkins-ci.plugins:build-publisher&lt;/p&gt;
&lt;p&gt;Jenkins Build-Publisher plugin version 1.21 and earlier stores credentials to other Jenkins instances in the file `hudson.plugins.build_publisher.BuildPublisher.xml` in the Jenkins master home directory. These credentials were stored unencrypted, allowing anyone with local file system access to access them. Additionally, the credentials were also transmitted in plain text as part of the configuration form. This could result in exposure of the credentials through browser extensions, cross-site scripting vulnerabilities, and similar situations. Build-Publisher Plugin 1.22 encrypts the credentials on disk, and only transmits their encrypted form to users viewing the configuration form.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: org.jenkins-ci.plugins:build-publisher&lt;/p&gt;
&lt;p&gt;Jenkins Build-Publisher plugin version 1.21 and earlier stores credentials to other Jenkins instances in the file `hudson.plugins.build_publisher.BuildPublisher.xml` in the Jenkins master home directory. These credentials were stored unencrypted, allowing anyone with local file system access to access them. Additionally, the credentials were also transmitted in plain text as part of the configuration form. This could result in exposure of the credentials through browser extensions, cross-site scripting vulnerabilities, and similar situations. Build-Publisher Plugin 1.22 encrypts the credentials on disk, and only transmits their encrypted form to users viewing the configuration form.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-m3wv-fr8v-fmh7</guid>
    </item>
    <item>
      <title>gsd-2017-1000387</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2017-1000387</link>
      <description>gsd-2017-1000387</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2017-1000387</guid>
    </item>
  </channel>
</rss>
