{"answers":{"affected":"5 open source packages ship an affected version, including hydra-core.","exploited":"There is no known exploitation of CVE-2026-106441 in the wild and no public exploit code.","fix":"Upgrade hydra-core to a fixed version for your release line: 1.3.6 or 1.4.0.dev9.","what":"CVE-2026-106441 is a high-severity code injection vulnerability in hydra-ecosystem hydra, published on 6 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-106441 and fix it if it is affected.\n\nWhat it is: CVE-2026-106441 is a high-severity code injection vulnerability in hydra-ecosystem hydra, published on 6 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-106441 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- hydra-core (PyPI): affected all versions; fixed in 1.3.6, 1.4.0.dev9\n- hydra-core (PyPI): affected all versions; fixed in 1.3.6\n- hydra-core (PyPI): affected all versions; fixed in 1.3.6\n- hydra-core (PyPI): affected from 1.4.0.dev0; fixed in 1.4.0.dev9\n- hydra-core (PyPI): affected from 1.4.0.dev0; fixed in 1.4.0.dev9\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-106441/ (Markdown: https://insights.sbomify.com/CVE-2026-106441/index.md)","id":"CVE-2026-106441","markdown":"https://insights.sbomify.com/CVE-2026-106441/index.md","name":"CVE-2026-106441","record":{"aliases":["GHSA-c3wx-c55w-pxjq","PYSEC-2026-4221"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Python configuration library","requires_auth":"none","summary":"Attackers controlling Hydra logging configuration can invoke arbitrary importable classes, leading to code execution with application privileges.","user_interaction":"required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"description":"Hydra is a framework for elegantly configuring complex applications. Prior to 1.3.6 and 1.4.0.dev9, Hydra passes Python logging configuration to logging.config.dictConfig() without applying Hydra's target policy to handler class values or formatter, filter, handler, queue, and listener factories. An attacker who controls Hydra logging configuration can therefore select an importable class or factory and cause it to be invoked with the application's privileges, even in versions where instantiate() is protected because the logging path does not use instantiate(). This issue is fixed in versions 1.3.6 and 1.4.0.dev9.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Hydra logging configuration permits unsafe callable resolution","id":"CVE-2026-106441","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":5,"n_references":4,"next":{"headline":"Hydra instantiate target blacklist bypasses permit code execution","id":"CVE-2026-106442"},"packages":[{"ecosystem":"PyPI","fixed":["1.3.6","1.4.0.dev9"],"introduced":["0","1.4.0.dev0"],"last_affected":[],"package":"hydra-core","purl":"pkg:pypi/hydra-core","source":"PYSEC-2026-4221"},{"ecosystem":"PyPI","fixed":["1.3.6"],"introduced":["0"],"last_affected":[],"package":"hydra-core","purl":null,"source":"GHSA-c3wx-c55w-pxjq"},{"ecosystem":"PyPI","fixed":["1.3.6"],"introduced":["0"],"last_affected":[],"package":"hydra-core","purl":"pkg:pypi/hydra-core","source":"GHSA-c3wx-c55w-pxjq"},{"ecosystem":"PyPI","fixed":["1.4.0.dev9"],"introduced":["1.4.0.dev0"],"last_affected":[],"package":"hydra-core","purl":null,"source":"GHSA-c3wx-c55w-pxjq"},{"ecosystem":"PyPI","fixed":["1.4.0.dev9"],"introduced":["1.4.0.dev0"],"last_affected":[],"package":"hydra-core","purl":"pkg:pypi/hydra-core","source":"GHSA-c3wx-c55w-pxjq"}],"prev":{"headline":"Hydra: Optuna custom_search_space can resolve and execute untrusted callables via get_method","id":"CVE-2026-106440"},"products":["hydra"],"published":"2026-10-06","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-07","vendors":["hydra-ecosystem"]},"summary":"Attackers controlling Hydra logging configuration can invoke arbitrary importable classes, leading to code execution with application privileges.","url":"https://insights.sbomify.com/CVE-2026-106441/"}