<?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 06:39:54 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-271274</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-271274</link>
      <description>EUVD-2026-271274</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-271274</guid>
    </item>
    <item>
      <title>fkie_cve-2025-10703</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-10703</link>
      <description>&lt;p&gt;Improper Control of Generation of Code (&amp;#39;Code Injection&amp;#39;) vulnerability in Progress DataDirect Connect for JDBC drivers, Progress DataDirect Open Access JDBC driver and Hybrid Data Pipeline allows Remote Code Inclusion.&lt;/p&gt;
&lt;p&gt;The SpyAttribute connection option implemented by the DataDirect Connect for JDBC drivers, DataDirect Hybrid Data Pipeline JDBC driver and the DataDirect OpenAccess JDBC driver log=(file) construct allows the user to specify an arbitrary file for the JDBC driver to write its log information to.  If an application allows an end user to specify a value for the SpyAttributes connection option then an attacker could cause java script to be written to a log file.  If the log file was in the correct location with the correct extension, an application server could see that log file as a resource to be served.  The attacker could fetch the resource from the server causing the java script to be executed.&lt;/p&gt;
&lt;p&gt;This issue affects:&lt;/p&gt;
&lt;p&gt;DataDirect Connect for JDBC for Amazon Redshift: through 6.0.0.001392, fixed in 6.0.0.001541&lt;/p&gt;
&lt;p&gt;DataDirect Connect for JDBC for Apache Cassandra: through 6.0.0.000805, fixed in 6.0.0.000833&lt;/p&gt;
&lt;p&gt;DataDirect Connect for JDBC for Hive: through 6.0.1.001499, fixed in 6.0.1.001628&lt;/p&gt;
&lt;p&gt;DataDirect Connect for JDBC for Apache Impala: through 6.0.0.001155, fixed in 6.0.0.001279&lt;/p&gt;
&lt;p&gt;DataDirect Connect for JDBC for Apache SparkSQL: through 6.0.1.001222, fixed in 6.0.1.001344&lt;/p&gt;
&lt;p&gt;DataDirect Connect for JDBC Autonomous REST Connector: through 6.0.1.006961, fixed in 6…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Improper Control of Generation of Code (&amp;#39;Code Injection&amp;#39;) vulnerability in Progress DataDirect Connect for JDBC drivers, Progress DataDirect Open Access JDBC driver and Hybrid Data Pipeline allows Remote Code Inclusion.&lt;/p&gt;
&lt;p&gt;The SpyAttribute connection option implemented by the DataDirect Connect for JDBC drivers, DataDirect Hybrid Data Pipeline JDBC driver and the DataDirect OpenAccess JDBC driver log=(file) construct allows the user to specify an arbitrary file for the JDBC driver to write its log information to.  If an application allows an end user to specify a value for the SpyAttributes connection option then an attacker could cause java script to be written to a log file.  If the log file was in the correct location with the correct extension, an application server could see that log file as a resource to be served.  The attacker could fetch the resource from the server causing the java script to be executed.&lt;/p&gt;
&lt;p&gt;This issue affects:&lt;/p&gt;
&lt;p&gt;DataDirect Connect for JDBC for Amazon Redshift: through 6.0.0.001392, fixed in 6.0.0.001541&lt;/p&gt;
&lt;p&gt;DataDirect Connect for JDBC for Apache Cassandra: through 6.0.0.000805, fixed in 6.0.0.000833&lt;/p&gt;
&lt;p&gt;DataDirect Connect for JDBC for Hive: through 6.0.1.001499, fixed in 6.0.1.001628&lt;/p&gt;
&lt;p&gt;DataDirect Connect for JDBC for Apache Impala: through 6.0.0.001155, fixed in 6.0.0.001279&lt;/p&gt;
&lt;p&gt;DataDirect Connect for JDBC for Apache SparkSQL: through 6.0.1.001222, fixed in 6.0.1.001344&lt;/p&gt;
&lt;p&gt;DataDirect Connect for JDBC Autonomous REST Connector: through 6.0.1.006961, fixed in 6…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-10703</guid>
    </item>
    <item>
      <title>GHSA-xrqq-74w4-x876</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-xrqq-74w4-x876</link>
      <description>&lt;p&gt;Improper Control of Generation of Code (&amp;#39;Code Injection&amp;#39;) vulnerability in Progress DataDirect Connect for JDBC drivers, Progress DataDirect Open Access JDBC driver and Hybrid Data Pipeline allows Remote Code Inclusion.&lt;/p&gt;
&lt;p&gt;The SpyAttribute connection option implemented by the DataDirect Connect for JDBC drivers, DataDirect Hybrid Data Pipeline JDBC driver and the DataDirect OpenAccess JDBC driver log=(file) construct allows the user to specify an arbitrary file for the JDBC driver to write its log information to.  If an application allows an end user to specify a value for the SpyAttributes connection option then an attacker could cause java script to be written to a log file.  If the log file was in the correct location with the correct extension, an application server could see that log file as a resource to be served.  The attacker could fetch the resource from the server causing the java script to be executed.&lt;/p&gt;
&lt;p&gt;This issue affects:&lt;/p&gt;
&lt;p&gt;DataDirect Connect for JDBC for Amazon Redshift: through 6.0.0.001392, fixed in 6.0.0.001541&lt;/p&gt;
&lt;p&gt;DataDirect Connect for JDBC for Apache Cassandra: through 6.0.0.000805, fixed in 6.0.0.000833&lt;/p&gt;
&lt;p&gt;DataDirect Connect for JDBC for Hive: through 6.0.1.001499, fixed in 6.0.1.001628&lt;/p&gt;
&lt;p&gt;DataDirect Connect for JDBC for Apache Impala: through 6.0.0.001155, fixed in 6.0.0.001279&lt;/p&gt;
&lt;p&gt;DataDirect Connect for JDBC for Apache SparkSQL: through 6.0.1.001222, fixed in 6.0.1.001344&lt;/p&gt;
&lt;p&gt;DataDirect Connect for JDBC Autonomous REST Connector: through 6.0.1.006961, fixed in 6…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Improper Control of Generation of Code (&amp;#39;Code Injection&amp;#39;) vulnerability in Progress DataDirect Connect for JDBC drivers, Progress DataDirect Open Access JDBC driver and Hybrid Data Pipeline allows Remote Code Inclusion.&lt;/p&gt;
&lt;p&gt;The SpyAttribute connection option implemented by the DataDirect Connect for JDBC drivers, DataDirect Hybrid Data Pipeline JDBC driver and the DataDirect OpenAccess JDBC driver log=(file) construct allows the user to specify an arbitrary file for the JDBC driver to write its log information to.  If an application allows an end user to specify a value for the SpyAttributes connection option then an attacker could cause java script to be written to a log file.  If the log file was in the correct location with the correct extension, an application server could see that log file as a resource to be served.  The attacker could fetch the resource from the server causing the java script to be executed.&lt;/p&gt;
&lt;p&gt;This issue affects:&lt;/p&gt;
&lt;p&gt;DataDirect Connect for JDBC for Amazon Redshift: through 6.0.0.001392, fixed in 6.0.0.001541&lt;/p&gt;
&lt;p&gt;DataDirect Connect for JDBC for Apache Cassandra: through 6.0.0.000805, fixed in 6.0.0.000833&lt;/p&gt;
&lt;p&gt;DataDirect Connect for JDBC for Hive: through 6.0.1.001499, fixed in 6.0.1.001628&lt;/p&gt;
&lt;p&gt;DataDirect Connect for JDBC for Apache Impala: through 6.0.0.001155, fixed in 6.0.0.001279&lt;/p&gt;
&lt;p&gt;DataDirect Connect for JDBC for Apache SparkSQL: through 6.0.1.001222, fixed in 6.0.1.001344&lt;/p&gt;
&lt;p&gt;DataDirect Connect for JDBC Autonomous REST Connector: through 6.0.1.006961, fixed in 6…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-xrqq-74w4-x876</guid>
    </item>
  </channel>
</rss>
