https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 20:42:58 +0000 https://cve.radiocsirt.org/vuln/bdu:2020-04842 bdu:2020-04842 https://cve.radiocsirt.org/vuln/bdu:2020-04842 https://cve.radiocsirt.org/vuln/cnvd-2020-49532 cnvd-2020-49532 https://cve.radiocsirt.org/vuln/cnvd-2020-49532 https://cve.radiocsirt.org/vuln/euvd-2026-163827 EUVD-2026-163827 https://cve.radiocsirt.org/vuln/euvd-2026-163827 https://cve.radiocsirt.org/vuln/fkie_cve-2020-5413 <p>Spring Integration framework provides Kryo Codec implementations as an alternative for Java (de)serialization. When Kryo is configured with default options, all unregistered classes are resolved on demand. This leads to the &#34;deserialization gadgets&#34; exploit when provided data contains malicious code for execution during deserialization. In order to protect against this type of attack, Kryo can be configured to require a set of trusted classes for (de)serialization. Spring Integration should be proactive against blocking unknown &#34;deserialization gadgets&#34; when configuring Kryo in code.</p> <p>Spring Integration framework provides Kryo Codec implementations as an alternative for Java (de)serialization. When Kryo is configured with default options, all unregistered classes are resolved on demand. This leads to the &#34;deserialization gadgets&#34; exploit when provided data contains malicious code for execution during deserialization. In order to protect against this type of attack, Kryo can be configured to require a set of trusted classes for (de)serialization. Spring Integration should be proactive against blocking unknown &#34;deserialization gadgets&#34; when configuring Kryo in code.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2020-5413 https://cve.radiocsirt.org/vuln/ghsa-86qr-9vqc-pgc6 <p><strong>Affected:</strong> Maven: org.springframework.integration:spring-integration-core</p> <p>Spring Integration framework provides Kryo Codec implementations as an alternative for Java (de)serialization. When Kryo is configured with default options, all unregistered classes are resolved on demand. This leads to the &#34;deserialization gadgets&#34; exploit when provided data contains malicious code for execution during deserialization. In order to protect against this type of attack, Kryo can be configured to require a set of trusted classes for (de)serialization. Spring Integration should be proactive against blocking unknown &#34;deserialization gadgets&#34; when configuring Kryo in code.</p> <p><strong>Affected:</strong> Maven: org.springframework.integration:spring-integration-core</p> <p>Spring Integration framework provides Kryo Codec implementations as an alternative for Java (de)serialization. When Kryo is configured with default options, all unregistered classes are resolved on demand. This leads to the &#34;deserialization gadgets&#34; exploit when provided data contains malicious code for execution during deserialization. In order to protect against this type of attack, Kryo can be configured to require a set of trusted classes for (de)serialization. Spring Integration should be proactive against blocking unknown &#34;deserialization gadgets&#34; when configuring Kryo in code.</p> https://cve.radiocsirt.org/vuln/ghsa-86qr-9vqc-pgc6 https://cve.radiocsirt.org/vuln/gsd-2020-5413 gsd-2020-5413 https://cve.radiocsirt.org/vuln/gsd-2020-5413