<?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, 05 Oct 2026 00:53:12 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-22741 — Static resource cache poisoning in Spring MVC and WebFlux</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-22741</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; VMware Spring Framework&lt;/p&gt;
&lt;p&gt;Spring MVC and WebFlux applications are vulnerable to cache poisoning when resolving static resources.&lt;/p&gt;
&lt;p&gt;More precisely, an application can be vulnerable when all the following are true:&lt;/p&gt;
&lt;p&gt;*  the application is using Spring MVC or Spring WebFlux
  *  the application is configuring the  resource chain support https://docs.spring.io/spring-framework/reference/web/webmvc/mvc-config/static-resources.html#page-title  with caching enabled
  *  the application adds support for encoded resources resolution
  *  the resource cache must be empty when the attacker has access to the application&lt;/p&gt;
&lt;p&gt;When all the conditions above are met, the attacker can send malicious requests and poison the resource cache with resources using the wrong encoding. This can cause a denial of service by breaking the front-end application for clients.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; VMware Spring Framework&lt;/p&gt;
&lt;p&gt;Spring MVC and WebFlux applications are vulnerable to cache poisoning when resolving static resources.&lt;/p&gt;
&lt;p&gt;More precisely, an application can be vulnerable when all the following are true:&lt;/p&gt;
&lt;p&gt;*  the application is using Spring MVC or Spring WebFlux
  *  the application is configuring the  resource chain support https://docs.spring.io/spring-framework/reference/web/webmvc/mvc-config/static-resources.html#page-title  with caching enabled
  *  the application adds support for encoded resources resolution
  *  the resource cache must be empty when the attacker has access to the application&lt;/p&gt;
&lt;p&gt;When all the conditions above are met, the attacker can send malicious requests and poison the resource cache with resources using the wrong encoding. This can cause a denial of service by breaking the front-end application for clients.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-22741</guid>
    </item>
    <item>
      <title>GHSA-3pxv-7cmr-fjr4 — Apache Log4j Core: Silent log event loss in XmlLayout due to unescaped XML 1.0 forbidden characters</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-3pxv-7cmr-fjr4</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: org.apache.logging.log4j:log4j-core&lt;/p&gt;
&lt;p&gt;Apache Log4j Core&amp;#39;s [`XmlLayout`](https://logging.apache.org/log4j/2.x/manual/layouts.html#XmlLayout), in versions up to and including 2.25.3, fails to sanitize characters forbidden by the [XML 1.0 specification](https://www.w3.org/TR/xml/#charsets), producing invalid XML output whenever a log message or MDC value contains such characters.&lt;/p&gt;
&lt;p&gt;The impact depends on the StAX implementation in use:&lt;/p&gt;
&lt;p&gt;*  **JRE built-in StAX**: Forbidden characters are silently written to the output, producing malformed XML. Conforming parsers must reject such documents with a fatal error, which may cause downstream log-processing systems to drop the affected records.
  *  **Alternative StAX implementations** (e.g., [Woodstox](https://github.com/FasterXML/woodstox), a transitive dependency of the Jackson XML Dataformat module): An exception is thrown during the logging call, and the log event is never delivered to its intended appender, only to Log4j&amp;#39;s internal status logger.&lt;/p&gt;
&lt;p&gt;Users are advised to upgrade to Apache Log4j Core 2.25.4, which corrects this issue by sanitizing forbidden characters before XML output.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: org.apache.logging.log4j:log4j-core&lt;/p&gt;
&lt;p&gt;Apache Log4j Core&amp;#39;s [`XmlLayout`](https://logging.apache.org/log4j/2.x/manual/layouts.html#XmlLayout), in versions up to and including 2.25.3, fails to sanitize characters forbidden by the [XML 1.0 specification](https://www.w3.org/TR/xml/#charsets), producing invalid XML output whenever a log message or MDC value contains such characters.&lt;/p&gt;
&lt;p&gt;The impact depends on the StAX implementation in use:&lt;/p&gt;
&lt;p&gt;*  **JRE built-in StAX**: Forbidden characters are silently written to the output, producing malformed XML. Conforming parsers must reject such documents with a fatal error, which may cause downstream log-processing systems to drop the affected records.
  *  **Alternative StAX implementations** (e.g., [Woodstox](https://github.com/FasterXML/woodstox), a transitive dependency of the Jackson XML Dataformat module): An exception is thrown during the logging call, and the log event is never delivered to its intended appender, only to Log4j&amp;#39;s internal status logger.&lt;/p&gt;
&lt;p&gt;Users are advised to upgrade to Apache Log4j Core 2.25.4, which corrects this issue by sanitizing forbidden characters before XML output.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-3pxv-7cmr-fjr4</guid>
    </item>
  </channel>
</rss>
