new file mode 100644
@@ -0,0 +1,55 @@
+From 414dab405a73c62e70306afc79de3529a1f2a4d0 Mon Sep 17 00:00:00 2001
+From: Byron <sebastian.thiel@icloud.com>
+Date: Mon, 10 Aug 2026 12:22:31 +0200
+Subject: [PATCH 30/38] fix: preserve multiline config values when writing
+
+<!-- agent -->
+GitConfigParser decoded valid multiline values into embedded newlines, but
+_write() serialized those newlines as indented physical lines. Rewriting an
+otherwise unchanged config could therefore change its meaning to Git.
+
+Serialize resident multiline values with Git-compatible escapes inside a
+quoted continuation, preserving GitPython read compatibility while keeping
+each option structurally intact. This addresses GHSA-284h-m62q-gf8w.
+
+The regression starts with an inert multiline value, performs an unrelated
+write, and verifies with both GitPython and git config that it remains one
+value and does not create another option.
+
+Git baseline: config.c parse_value() and write_pair() at cf5497b14c5a escape
+embedded LF as \\n rather than emitting it as a physical config line.
+
+CVE: CVE-2026-78676
+Upstream-Status: Backport [https://github.com/gitpython-developers/GitPython/commit/4b4e47fc1224e23b0c8ee7220a7192818f2e4abb]
+
+Backport Changes:
+- Omit upstream regression test changes because the current PyPI
+ source archive does not include its test suite.
+
+Assisted-by: GPT 5.6
+Co-authored-by: GPT 5.6 <codex@openai.com>
+(cherry picked from commit 4b4e47fc1224e23b0c8ee7220a7192818f2e4abb)
+Signed-off-by: Yogita Urade <yurade@cisco.com>
+---
+ git/config.py | 6 +++++-
+ 1 file changed, 5 insertions(+), 1 deletion(-)
+
+diff --git a/git/config.py b/git/config.py
+index ff88bd18..cc7091dd 100644
+--- a/git/config.py
++++ b/git/config.py
+@@ -665,7 +665,11 @@ class GitConfigParser(cp.RawConfigParser, metaclass=MetaParserBuilder):
+ continue
+
+ for v in values:
+- fp.write(("\t%s = %s\n" % (key, self._value_to_string(v).replace("\n", "\n\t"))).encode(defenc))
++ value = self._value_to_string(v)
++ if any(char in value for char in '\n\t\b\\"'):
++ value = value.replace("\\", "\\\\").replace('"', '\\"')
++ value = '"%s\\\n"' % value.replace("\n", "\\n").replace("\t", "\\t").replace("\b", "\\b")
++ fp.write(("\t%s = %s\n" % (key, value)).encode(defenc))
+ # END if key is not __name__
+
+ # END section writing
+--
+2.35.6
@@ -45,6 +45,7 @@ SRC_URI += " file://CVE-2026-42284.patch \
file://CVE-2026-76222_p2.patch \
file://CVE-2026-78678_CVE-2026-78679.patch \
file://CVE-2026-78677.patch \
+ file://CVE-2026-78676.patch \
"
SRC_URI[sha256sum] = "2d99869e0fef71a73cbd242528105af1d6c1b108c60dfabd994bf292f76c3ceb"
This patch applies the upstream fix as referenced in [2], using the commit shown in [1]. [1] https://github.com/gitpython-developers/GitPython/commit/4b4e47fc1224e23b0c8ee7220a7192818f2e4abb [2] https://www.cve.org/CVERecord?id=CVE-2026-78676 Signed-off-by: Yogita Urade <yurade@cisco.com> --- .../python/python3-git/CVE-2026-78676.patch | 55 +++++++++++++++++++ .../python/python3-git_3.1.42.bb | 1 + 2 files changed, 56 insertions(+) create mode 100644 meta/recipes-devtools/python/python3-git/CVE-2026-78676.patch