<?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, 03 Oct 2026 22:06:45 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-344258</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-344258</link>
      <description>EUVD-2026-344258</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-344258</guid>
    </item>
    <item>
      <title>fkie_cve-2024-2700</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-2700</link>
      <description>&lt;p&gt;A vulnerability was found in the quarkus-core component. Quarkus captures local environment variables from the Quarkus namespace during the application&amp;#39;s build, therefore, running the resulting application inherits the values captured at build time. Some local environment variables may have been set by the developer or CI environment for testing purposes, such as dropping the database during application startup or trusting all TLS certificates to accept self-signed certificates. If these properties are configured using environment variables or the .env facility, they are captured into the built application, which can lead to dangerous behavior if the application does not override these values. This behavior only happens for configuration properties from the `quarkus.*` namespace. Application-specific properties are not captured.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;A vulnerability was found in the quarkus-core component. Quarkus captures local environment variables from the Quarkus namespace during the application&amp;#39;s build, therefore, running the resulting application inherits the values captured at build time. Some local environment variables may have been set by the developer or CI environment for testing purposes, such as dropping the database during application startup or trusting all TLS certificates to accept self-signed certificates. If these properties are configured using environment variables or the .env facility, they are captured into the built application, which can lead to dangerous behavior if the application does not override these values. This behavior only happens for configuration properties from the `quarkus.*` namespace. Application-specific properties are not captured.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-2700</guid>
    </item>
    <item>
      <title>GHSA-f8h5-v2vg-46rr — quarkus-core leaks local environment variables from Quarkus namespace during application's build</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-f8h5-v2vg-46rr</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: io.quarkus:quarkus-core&lt;/p&gt;
&lt;p&gt;A vulnerability was found in the quarkus-core component. Quarkus captures the local environment variables from the Quarkus namespace during the application&amp;#39;s build. Thus, running the resulting application inherits the values captured at build time.&lt;/p&gt;
&lt;p&gt;However, some local environment variables may have been set by the developer / CI environment for testing purposes, such as dropping the database during the application startup or trusting all TLS certificates to accept self-signed certificates. If these properties are configured using environment variables or the .env facility, they are captured into the built application. It may lead to dangerous behavior if the application does not override these values.&lt;/p&gt;
&lt;p&gt;This behavior only happens for configuration properties from the `quarkus.*` namespace. So, application-specific properties are not captured.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: io.quarkus:quarkus-core&lt;/p&gt;
&lt;p&gt;A vulnerability was found in the quarkus-core component. Quarkus captures the local environment variables from the Quarkus namespace during the application&amp;#39;s build. Thus, running the resulting application inherits the values captured at build time.&lt;/p&gt;
&lt;p&gt;However, some local environment variables may have been set by the developer / CI environment for testing purposes, such as dropping the database during the application startup or trusting all TLS certificates to accept self-signed certificates. If these properties are configured using environment variables or the .env facility, they are captured into the built application. It may lead to dangerous behavior if the application does not override these values.&lt;/p&gt;
&lt;p&gt;This behavior only happens for configuration properties from the `quarkus.*` namespace. So, application-specific properties are not captured.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-f8h5-v2vg-46rr</guid>
    </item>
    <item>
      <title>gsd-2024-2700</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2024-2700</link>
      <description>gsd-2024-2700</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2024-2700</guid>
    </item>
    <item>
      <title>RHSA-2024:11023 — Red Hat Security Advisory: HawtIO 4.1.0 for Red Hat build of Apache Camel 4 Release and security update.</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2024:11023</link>
      <description>&lt;p&gt;quarkus-core: Leak of local configuration properties into Quarkus applications braces: fails to limit the number of characters it can handle undertow: Improper State Management in Proxy Protocol parsing causes information leakage org.eclipse.jetty:jetty-server: jetty: Jetty ThreadLimitHandler.getRemote() vulnerable to remote DoS attacks spring-webmvc: Path Traversal Vulnerability in Spring Applications Using RouterFunctions and FileSystemResource express: Improper Input Handling in Express Redirects send: Code Execution Vulnerability in Send Library serve-static: Improper Sanitization in serve-static path-to-regexp: Backtracking regular expressions cause ReDoS&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;quarkus-core: Leak of local configuration properties into Quarkus applications braces: fails to limit the number of characters it can handle undertow: Improper State Management in Proxy Protocol parsing causes information leakage org.eclipse.jetty:jetty-server: jetty: Jetty ThreadLimitHandler.getRemote() vulnerable to remote DoS attacks spring-webmvc: Path Traversal Vulnerability in Spring Applications Using RouterFunctions and FileSystemResource express: Improper Input Handling in Express Redirects send: Code Execution Vulnerability in Send Library serve-static: Improper Sanitization in serve-static path-to-regexp: Backtracking regular expressions cause ReDoS&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2024:11023</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-1068 — Red Hat Enterprise Linux (Quarkus and Netty): Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1068</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Red Hat OpenShift und Red Hat Enterprise Linux ausnutzen, um Informationen offenzulegen oder einen Denial-of-Service-Zustand zu verursachen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Red Hat OpenShift und Red Hat Enterprise Linux ausnutzen, um Informationen offenzulegen oder einen Denial-of-Service-Zustand zu verursachen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1068</guid>
    </item>
  </channel>
</rss>
