Search

Find a vulnerability

Search criteria ⓘ Use this form to refine search results.
Full-text search supports keyword queries with ranking and filtering.
You can combine vendor, product, and sources to narrow results.
Enable “Apply ordering” to sort by date instead of relevance.

    6 vulnerabilities found for python-dulwich by azure linux

    AZL-112720 (CVE-2026-122299)

    Vulnerability from osv_azurelinux – Published: 2026-11-04 23:17 – Updated: 2026-11-18 05:27 – Source website
    VLAI
    Summary
    CVE-2026-122299 affecting package python-dulwich 0.21.7-6
    Details

    Dulwich before 1.2.20 contains a commit object parsing vulnerability where the read path in _parse_commit resolves a duplicate tree header to the last occurrence instead of the first, diverging from core git's resolution behavior, while Poetry 2.5.1 ships this version and uses dulwich by default for git dependency installation. Attackers can craft a commit object with two tree headers so that reviewers and CI using git see a benign tree while Poetry's dulwich-based checkout resolves to a different attacker-controlled tree containing malicious build scripts such as setup.py, resulting in unreviewed code execution on the install or build host.

    Upstream
    References
    Impacted products
    Ecosystem Package Version
    Azure Linux:3 python-dulwich
    pkg:rpm/azure-linux/python-dulwich
    Affected: ≤ 0.21.7-6 (ecosystem)

    {
      "affected": [
        {
          "package": {
            "ecosystem": "Azure Linux:3",
            "name": "python-dulwich",
            "purl": "pkg:rpm/azure-linux/python-dulwich"
          },
          "ranges": [
            {
              "events": [
                {
                  "introduced": "0"
                },
                {
                  "last_affected": "0.21.7-6"
                }
              ],
              "type": "ECOSYSTEM"
            }
          ]
        }
      ],
      "details": "Dulwich before 1.2.20 contains a commit object parsing vulnerability where the read path in _parse_commit resolves a duplicate tree header to the last occurrence instead of the first, diverging from core git\u0027s resolution behavior, while Poetry 2.5.1 ships this version and uses dulwich by default for git dependency installation. Attackers can craft a commit object with two tree headers so that reviewers and CI using git see a benign tree while Poetry\u0027s dulwich-based checkout resolves to a different attacker-controlled tree containing malicious build scripts such as setup.py, resulting in unreviewed code execution on the install or build host.",
      "id": "AZL-112720",
      "modified": "2026-11-18T05:27:31Z",
      "published": "2026-11-04T23:17:23Z",
      "references": [
        {
          "type": "WEB",
          "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-122299"
        }
      ],
      "schema_version": "1.7.4",
      "summary": "CVE-2026-122299 affecting package python-dulwich 0.21.7-6",
      "upstream": [
        "CVE-2026-122299"
      ]
    }

    AZL-109893 (CVE-2026-114095)

    Vulnerability from osv_azurelinux – Published: 2026-10-21 01:17 – Updated: 2026-11-18 05:27 – Source website
    VLAI
    Summary
    CVE-2026-114095 affecting package python-dulwich 0.21.7-6
    Details

    Dulwich before 1.2.9 contains a denial of service vulnerability in Pack.resolve_object that allows attackers to cause infinite recursion via self-referential OFS_DELTA objects. Attackers can supply a malicious packfile with an OFS_DELTA delta_offset of 0 to exhaust CPU during clone, fetch, or cat-file operations.

    Upstream
    References
    Impacted products
    Ecosystem Package Version
    Azure Linux:3 python-dulwich
    pkg:rpm/azure-linux/python-dulwich
    Affected: ≤ 0.21.7-6 (ecosystem)

    {
      "affected": [
        {
          "package": {
            "ecosystem": "Azure Linux:3",
            "name": "python-dulwich",
            "purl": "pkg:rpm/azure-linux/python-dulwich"
          },
          "ranges": [
            {
              "events": [
                {
                  "introduced": "0"
                },
                {
                  "last_affected": "0.21.7-6"
                }
              ],
              "type": "ECOSYSTEM"
            }
          ]
        }
      ],
      "details": "Dulwich before 1.2.9 contains a denial of service vulnerability in Pack.resolve_object that allows attackers to cause infinite recursion via self-referential OFS_DELTA objects. Attackers can supply a malicious packfile with an OFS_DELTA delta_offset of 0 to exhaust CPU during clone, fetch, or cat-file operations.",
      "id": "AZL-109893",
      "modified": "2026-11-18T05:27:31Z",
      "published": "2026-10-21T01:17:34Z",
      "references": [
        {
          "type": "WEB",
          "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-114095"
        }
      ],
      "schema_version": "1.7.4",
      "summary": "CVE-2026-114095 affecting package python-dulwich 0.21.7-6",
      "upstream": [
        "CVE-2026-114095"
      ]
    }

    AZL-109890 (CVE-2026-114094)

    Vulnerability from osv_azurelinux – Published: 2026-10-21 01:17 – Updated: 2026-11-18 05:27 – Source website
    VLAI
    Summary
    CVE-2026-114094 affecting package python-dulwich 0.21.7-6
    Details

    Dulwich before 1.2.9 fails to validate DOS drive letter prefixes in Git tree path elements on Windows, allowing arbitrary file write. Attackers can craft a malicious repository with a tree entry named 'C:' that bypasses NTFS validation and writes files outside the worktree to achieve remote code execution.

    Upstream
    References
    Impacted products
    Ecosystem Package Version
    Azure Linux:3 python-dulwich
    pkg:rpm/azure-linux/python-dulwich
    Affected: ≤ 0.21.7-6 (ecosystem)

    {
      "affected": [
        {
          "package": {
            "ecosystem": "Azure Linux:3",
            "name": "python-dulwich",
            "purl": "pkg:rpm/azure-linux/python-dulwich"
          },
          "ranges": [
            {
              "events": [
                {
                  "introduced": "0"
                },
                {
                  "last_affected": "0.21.7-6"
                }
              ],
              "type": "ECOSYSTEM"
            }
          ]
        }
      ],
      "details": "Dulwich before 1.2.9 fails to validate DOS drive letter prefixes in Git tree path elements on Windows, allowing arbitrary file write. Attackers can craft a malicious repository with a tree entry named \u0027C:\u0027 that bypasses NTFS validation and writes files outside the worktree to achieve remote code execution.",
      "id": "AZL-109890",
      "modified": "2026-11-18T05:27:31Z",
      "published": "2026-10-21T01:17:34Z",
      "references": [
        {
          "type": "WEB",
          "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-114094"
        }
      ],
      "schema_version": "1.7.4",
      "summary": "CVE-2026-114094 affecting package python-dulwich 0.21.7-6",
      "upstream": [
        "CVE-2026-114094"
      ]
    }

    AZL-92481 (CVE-2026-38974)

    Vulnerability from osv_azurelinux – Published: 2026-07-15 22:16 – Updated: 2026-11-18 05:27 – Source website
    VLAI
    Summary
    CVE-2026-38974 affecting package python-dulwich 0.21.7-6
    Details

    Dulwich through 1.1.0 was found to be missing SSH host key verification in contrib/paramiko_vendor.py.

    Upstream
    References
    Impacted products
    Ecosystem Package Version
    Azure Linux:3 python-dulwich
    pkg:rpm/azure-linux/python-dulwich
    Affected: ≤ 0.21.7-6 (ecosystem)

    {
      "affected": [
        {
          "package": {
            "ecosystem": "Azure Linux:3",
            "name": "python-dulwich",
            "purl": "pkg:rpm/azure-linux/python-dulwich"
          },
          "ranges": [
            {
              "events": [
                {
                  "introduced": "0"
                },
                {
                  "last_affected": "0.21.7-6"
                }
              ],
              "type": "ECOSYSTEM"
            }
          ]
        }
      ],
      "details": "Dulwich through 1.1.0 was found to be missing SSH host key verification in contrib/paramiko_vendor.py.",
      "id": "AZL-92481",
      "modified": "2026-11-18T05:27:31Z",
      "published": "2026-07-15T22:16:47Z",
      "references": [
        {
          "type": "WEB",
          "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-38974"
        }
      ],
      "schema_version": "1.7.4",
      "summary": "CVE-2026-38974 affecting package python-dulwich 0.21.7-6",
      "upstream": [
        "CVE-2026-38974"
      ]
    }

    AZL-90077 (CVE-2026-47734)

    Vulnerability from osv_azurelinux – Published: 2026-06-10 23:16 – Updated: 2026-11-18 05:27 – Source website
    VLAI
    Summary
    CVE-2026-47734 affecting package python-dulwich 0.21.7-6
    Details

    Dulwich is a pure-Python implementation of the Git file formats and protocols. Starting in version 0.1.0 and prior to version 1.2.5, a client with push access could push a tiny crafted thin pack (~174 bytes) whose delta header declares a huge dest_size. When dulwich ingested it via add_thin_pack / apply_delta, it would allocate hundreds of MB of memory based on that attacker-controlled size, with no relationship to the actual bytes received. Operators running a Dulwich-based Git server that exposes git-receive-pack (i.e. accepts pushes) - for example via dulwich.server functionality, the HTTP smart server, or anything built on ReceivePackHandler - are impacted. The issue is patched in 1.2.5. add_thin_pack now accepts a max_input_size keyword (bytes; 0/None = unlimited, matching git's semantics), and ReceivePackHandler reads receive.maxInputSize from the repository config and passes it through. Wire reads are counted and a PackInputTooLarge exception is raised once the cap is exceeded - equivalent to git index-pack --max-input-size. Users should upgrade to Dulwich 1.2.5 or later and set receive.maxInputSize in their server's repository config to a sane bound for their environment. On unpatched versions, receive.maxInputSize has no effect, so it cannot be used as a workaround. Until upgrading, operators should restrict dulwich-receive-pack (push) access to trusted, authenticated clients only, or disable it entirely on servers that only need to serve fetches and/or run the server under an OS-level memory limit (e.g. ulimit, cgroups/MemoryMax, or a container memory limit) so a malicious push is killed rather than taking down the host.

    Upstream
    References
    Impacted products
    Ecosystem Package Version
    Azure Linux:3 python-dulwich
    pkg:rpm/azure-linux/python-dulwich
    Affected: ≤ 0.21.7-6 (ecosystem)

    {
      "affected": [
        {
          "package": {
            "ecosystem": "Azure Linux:3",
            "name": "python-dulwich",
            "purl": "pkg:rpm/azure-linux/python-dulwich"
          },
          "ranges": [
            {
              "events": [
                {
                  "introduced": "0"
                },
                {
                  "last_affected": "0.21.7-6"
                }
              ],
              "type": "ECOSYSTEM"
            }
          ]
        }
      ],
      "details": "Dulwich is a pure-Python implementation of the Git file formats and protocols. Starting in version 0.1.0 and prior to version 1.2.5, a client with push access could push a tiny crafted thin pack (~174 bytes)  whose delta header declares a huge   dest_size. When dulwich ingested it via  add_thin_pack / apply_delta, it would  allocate hundreds of MB of memory based on that attacker-controlled size, with no relationship to the actual bytes received. Operators running a Dulwich-based Git server that exposes git-receive-pack (i.e. accepts pushes) - for example via dulwich.server functionality, the HTTP  smart server, or anything built on ReceivePackHandler - are impacted. The issue is patched in 1.2.5. add_thin_pack now accepts a max_input_size keyword (bytes; 0/None = unlimited, matching git\u0027s semantics), and ReceivePackHandler reads receive.maxInputSize from the repository config and passes it through. Wire reads are counted and a PackInputTooLarge exception is raised once the cap is exceeded - equivalent to git index-pack --max-input-size. Users should upgrade to Dulwich 1.2.5 or later and set receive.maxInputSize in their server\u0027s repository config to a sane bound for their environment. On unpatched versions, receive.maxInputSize has no effect, so it cannot be used as a workaround. Until upgrading, operators should restrict dulwich-receive-pack (push) access to trusted, authenticated clients only, or disable it entirely on servers that only need to serve fetches and/or run the server under an OS-level memory limit (e.g. ulimit, cgroups/MemoryMax, or a container memory limit) so a malicious push is killed rather than taking down the host.",
      "id": "AZL-90077",
      "modified": "2026-11-18T05:27:31Z",
      "published": "2026-06-10T23:16:48Z",
      "references": [
        {
          "type": "WEB",
          "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-47734"
        }
      ],
      "schema_version": "1.7.4",
      "summary": "CVE-2026-47734 affecting package python-dulwich 0.21.7-6",
      "upstream": [
        "CVE-2026-47734"
      ]
    }

    AZL-90074 (CVE-2026-42305)

    Vulnerability from osv_azurelinux – Published: 2026-06-10 23:16 – Updated: 2026-11-18 05:27 – Source website
    VLAI
    Summary
    CVE-2026-42305 affecting package python-dulwich 0.21.7-6
    Details

    Dulwich is a pure-Python implementation of the Git file formats and protocols. Versions starting with 0.10.0 and prior to 1.2.5 have an arbitrary file write leading to remote code execution when cloning or checking out a malicious Git repository on Windows. Dulwich's path-element validator accepted tree entries whose filenames contained bytes that Windows interprets as structural path syntax. Contributing configuration bugs made matters worse. The core.protectNTFS and core.protectHFS settings were looked up under a wrong option name and so user-set values were silently ignored, and core.protectNTFS only defaulted to true on Windows (Git upstream has defaulted it to true everywhere since CVE-2019-1353). Both have been corrected. Anyone who clones, fetches, or checks out an untrusted repository with Dulwich on Windows - either through the Dulwich CLI, porcelain.clone, or any downstream tool built on Dulwich - is impacted. POSIX clones are not directly exploitable (on POSIX \ is a literal filename byte), but a POSIX user can unknowingly propagate a malicious tree to Windows consumers via push or re-publication. This issue is fixed in Dulwich 1.2.5. Users should upgrade to 1.2.5 or later. There is no effective pre-patch workaround. On affected versions the core.protectNTFS configuration key was silently ignored, so setting it to true does not mitigate the issue. Users who cannot upgrade should avoid cloning, fetching, or checking out untrusted repositories with Dulwich on Windows. After upgrading the NTFS validator is on by default on every platform, so no additional configuration is required.

    Upstream
    References
    Impacted products
    Ecosystem Package Version
    Azure Linux:3 python-dulwich
    pkg:rpm/azure-linux/python-dulwich
    Affected: ≤ 0.21.7-6 (ecosystem)

    {
      "affected": [
        {
          "package": {
            "ecosystem": "Azure Linux:3",
            "name": "python-dulwich",
            "purl": "pkg:rpm/azure-linux/python-dulwich"
          },
          "ranges": [
            {
              "events": [
                {
                  "introduced": "0"
                },
                {
                  "last_affected": "0.21.7-6"
                }
              ],
              "type": "ECOSYSTEM"
            }
          ]
        }
      ],
      "details": "Dulwich is a pure-Python implementation of the Git file formats and protocols. Versions starting with 0.10.0 and prior to 1.2.5 have an arbitrary file write leading to remote code execution when cloning or checking out a malicious Git repository on Windows. Dulwich\u0027s path-element validator accepted tree entries whose filenames contained bytes that Windows interprets as structural path syntax. Contributing configuration bugs made matters worse. The core.protectNTFS and core.protectHFS settings were looked up under a wrong option name and so user-set values were silently ignored, and core.protectNTFS only defaulted to true on Windows (Git upstream has defaulted it to true everywhere since CVE-2019-1353). Both have been corrected. Anyone who clones, fetches, or checks out an untrusted repository with Dulwich on Windows - either through the Dulwich CLI, porcelain.clone, or any downstream tool built on Dulwich - is impacted. POSIX clones are not directly exploitable (on POSIX \\ is a literal filename byte), but a POSIX user can unknowingly propagate a malicious tree to Windows consumers via push or re-publication. This issue is fixed in Dulwich 1.2.5. Users should upgrade to 1.2.5 or later. There is no effective pre-patch workaround. On affected versions the core.protectNTFS configuration key was silently ignored, so setting it to true does not mitigate the issue. Users who cannot upgrade should avoid cloning, fetching, or checking out untrusted repositories with Dulwich on Windows. After upgrading the NTFS validator is on by default on every platform, so no additional configuration is required.",
      "id": "AZL-90074",
      "modified": "2026-11-18T05:27:31Z",
      "published": "2026-06-10T23:16:46Z",
      "references": [
        {
          "type": "WEB",
          "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-42305"
        }
      ],
      "schema_version": "1.7.4",
      "summary": "CVE-2026-42305 affecting package python-dulwich 0.21.7-6",
      "upstream": [
        "CVE-2026-42305"
      ]
    }