Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Low, CVSS 3.3amended

Dulwich doesn't sanitize commit subjects in porcelain.format_patch

CVE-2026-47712GHSA-555p-6grf-mh7f

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (dulwich 1.2.5), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • PyPI dulwich

    Affected
    >= 0.24.0, < 1.2.5
    Fixed in
    1.2.5

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
3.3 · CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
EPSS
  • CVE-2026-47712: 0.14% estimated exploitation activity in the next 30 days; percentile 3.25 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Impact dulwich.porcelain.formatpatch(outdir=...) derives each patch filename from the commit's subject line. Prior to this fix, getsummary only replaced spaces with dashes - path separators (/, \), parent-directory components (..), and other filename-hostile characters (e.g. :) were preserved verbatim and passed straight into os.path.join(outdir, f"{i:04d}-{summary}.patch"). A malicious commit subject could therefore direct the generated patch file outside the requested outdir. Reduced examples: - x/../../x produced <outdir/0001-x/../../x.patch, resolving two directories above outdir. - x\..\..\x produced the equivalent escape on Windows, here \ is also a path separator. Related issues from the same root cause: - Subjects containing characters that are illegal in Windows filenames (e.g. :) caused formatpatch to fail outright on Windows, where git would have succeeded. - Very long subjects produced excessively long filenames that could exceed filesystem limits; git truncates them.…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-555p-6grf-mh7f

  2. Revision 1 · created ·

    Published from osv record GHSA-555p-6grf-mh7f

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-47712

Advisory: Dulwich doesn't sanitize commit subjects in `porcelain.format_patch`
IDs: CVE-2026-47712, GHSA-555p-6grf-mh7f
Record: https://patchnext.com/advisories/cve-2026-47712 (revision 2, source checked 26 Oct 2026, 13:45 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 3.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: dulwich 1.2.5. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI dulwich: affected >= 0.24.0, < 1.2.5; fixed in 1.2.5

## Suggested inspection (read-only)
- `python -m pip show dulwich`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on dulwich.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-555p-6grf-mh7f (OSV record GHSA-555p-6grf-mh7f lists affected ranges: PyPI dulwich >=0.24.0 <1.2.5 (fixed))
- Verified: https://github.com/advisories/GHSA-555p-6grf-mh7f (GitHub-reviewed advisory GHSA-555p-6grf-mh7f lists affected ranges: PyPI dulwich >=0.24.0 <1.2.5)

Commands are suggestions: review each one before running it.

Loading voting…