<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-02T16:22:26.462859+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cve-2026-35171</id>
    <title>CVE-2026-35171 — Arbitrary Code Execution via Malicious Logging Configuration in Kedro</title>
    <updated>2026-10-02T16:22:26.464770+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> kedro-org kedro</p>
<p>Kedro is a toolbox for production-ready data science. Prior to 1.3.0, Kedro allows the logging configuration file path to be set via the KEDRO_LOGGING_CONFIG environment variable and loads it without validation. The logging configuration schema supports the special () key, which enables arbitrary callable instantiation. An attacker can exploit this to execute arbitrary system commands during application startup. This is a critical remote code execution (RCE) vulnerability caused by unsafe use of logging.config.dictConfig() with user-controlled input. This vulnerability is fixed in 1.3.0.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2026-35171"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-9cqf-439c-j96r</id>
    <title>GHSA-9cqf-439c-j96r — Kedro has Arbitrary Code Execution via Malicious Logging Configuration</title>
    <updated>2026-10-02T16:22:26.464854+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: kedro</p>
<p>### Impact</p>
<p>This is a **critical remote code execution (RCE)** vulnerability caused by unsafe use of `logging.config.dictConfig()` with user-controlled input.</p>
<p>Kedro allows the logging configuration file path to be set via the `KEDRO_LOGGING_CONFIG` environment variable and loads it without validation. The logging configuration schema supports the special `()` key, which enables arbitrary callable instantiation. An attacker can exploit this to execute arbitrary system commands during application startup.</p>
<p>---</p>
<p>### Patches</p>
<p>The vulnerability is fixed by introducing validation that rejects the unsafe `()` factory key in logging configurations before passing them to `dictConfig()`.</p>
<p>#### Fixed in
- Kedro 1.3.0</p>
<p>Users should upgrade to this version as soon as possible.</p>
<p>---</p>
<p>### Workarounds</p>
<p>If upgrading is not immediately possible:</p>
<p>- Do not allow untrusted input to control the `KEDRO_LOGGING_CONFIG` environment variable  
- Restrict write access to logging configuration files  
- Avoid using externally supplied or dynamically generated logging configs  
- Manually validate logging YAML to ensure it does not contain the `()` key</p>
<p>These mitigations reduce risk but do not fully eliminate it.</p>
<p>---</p>
<p>### References</p>
<p>- Python logging configuration documentation: https://docs.python.org/3/library/logging.config.html#logging-config-dictschema  
- CWE-94: Code Injection — https://cwe.mitre.org/data/definitions/94.html</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-9cqf-439c-j96r"/>
  </entry>
</feed>
