KedroApplication · Linuxfoundation
CVE-2026-35171
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedKedro 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceKedro versions prior to 1.3.0 load logging configuration from the KEDRO_LOGGING_CONFIG environment variable without validation. The logging.config.dictConfig() function supports a special () key that enables arbitrary callable instantiation, allowing attackers to execute system commands during application startup via malicious logging configuration.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
KedroApplication
< 1.3.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Determine installed Kedro versionRun 'pip show kedro' or 'kedro --version' to retrieve the installed version numberAffected if The installed version is less than 1.3.0
-
Check if KEDRO_LOGGING_CONFIG is setRun 'echo $KEDRO_LOGGING_CONFIG' in the shell or inspect os.environ.get('KEDRO_LOGGING_CONFIG') in PythonAffected if The KEDRO_LOGGING_CONFIG environment variable contains any value
-
Inspect the logging configuration contentIf KEDRO_LOGGING_CONFIG is set, examine the file path or content it points to. Check for the presence of the '()' key in the configuration dictionary, which enables callable instantiationAffected if The configuration contains the '()' key with a callable that executes system commands
-
Verify the source of KEDRO_LOGGING_CONFIGReview how the KEDRO_LOGGING_CONFIG environment variable is being set in your deployment pipeline, scripts, or shell configuration filesAffected if The variable is set from untrusted or external input sources such as user-provided environment variables, unvalidated config files, or untrusted deployment configurations
You are affected if Kedro version is below 1.3.0 AND the KEDRO_LOGGING_CONFIG environment variable is set to a value that originates from an untrusted source or contains callable ('()') configurations.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.3.0
Upgrade Kedro to version 1.3.0 or later. Until then, ensure the KEDRO_LOGGING_CONFIG environment variable is not set to untrusted values and that no user-controlled logging config files are used.
Kedro 1.3.0
- Check current Kedro version using 'pip show kedro' or 'kedro --version'
- Upgrade Kedro to version 1.3.0 or later using 'pip install --upgrade kedro>=1.3.0'
- Verify the upgrade was successful by running 'kedro --version'
- Ensure any KEDRO_LOGGING_CONFIG environment variables point to trusted, non-user-controlled configuration files
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Kedro
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,144.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-35171 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-35171 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data