GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — [GHSA-3rp5-jjmw-4wv2] GitPython: git-config section-name injection enables arbitrary config directives (core.sshCommand RCE) by ranjiGT · Pull Request #10326 · github/advisory-database

Conversation

@ranjiGT

@ranjiGT ranjiGT commented Oct 12, 2026

Copy link
Copy Markdown

Updates

  • References

Comments

Reason for Change

Adds a direct reference to upstream GitPython pull request #2176
for GHSA-3rp5-jjmw-4wv2.

The pull request is associated with the existing security-fix commit
1ed1b924f4e2d2ee7bab296df77b978af21853f1, titled
"fix: validate config section delimiters."

This additional reference improves traceability between the
vulnerability, its upstream remediation, and the GitPython 3.1.53
release.

Supporting Evidence

  • Upstream fix PR: fix: validate config section delimiters gitpython-developers/GitPython#2176
  • Security fix commit: gitpython-developers/GitPython@1ed1b92
  • Patched release: https://github.com/gitpython-developers/GitPython/releases/tag/3.1.53
  • Upstream security advisory: GHSA-3rp5-jjmw-4wv2

Scope of Change

This contribution adds only the upstream pull request reference.

No changes are proposed to:

  • Vulnerability description
  • Affected versions: <= 3.1.52
  • Patched version: 3.1.53
  • CVSS severity: High (7.0)
  • CWE classification: CWE-74
  • Source repository: https://github.com/gitpython-developers/GitPython

This is a documentation-only improvement intended to strengthen
the advisory's upstream references and improve security-fix traceability.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.
All reactions
@ranjiGT
Improve GHSA-3rp5-jjmw-4wv2
1147b60
@github

github commented Oct 12, 2026

Copy link
Copy Markdown
Collaborator

Hi there @Byron! A community member has suggested an improvement to your security advisory. If approved, this change will affect the global advisory listed at github.com/advisories. It will not affect the version listed in your project repository.

This change will be reviewed by our Security Curation Team. If you have thoughts or feedback, please share them in a comment here! If this PR has already been closed, you can start a new community contribution for this advisory
All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.
Copilot AI balanced review requested due to automatic review settings October 12, 2026 13:56
Copilot started reviewing on behalf of ranjiGT October 12, 2026 13:57
View session
@github-actions
github-actions Bot changed the base branch from main to ranjiGT/advisory-improvement-10326 October 12, 2026 13:57
Copilot AI reviewed Oct 12, 2026
View reviewed changes

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

There was a problem hiding this comment.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

The added reference correctly links to the merged pull request containing the existing security-fix commit.

0 open findings

What changed in this PR

Adds the upstream GitPython remediation pull request to improve advisory traceability.

Changes:

  • Adds GitPython PR #2176 as a reference.
  • Updates the advisory modification timestamp.
File Description
GHSA-3rp5-jjmw-4wv2.json Adds the verified upstream fix PR reference.

🧠 Review effort: Balanced

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.
All reactions
Byron
Byron approved these changes Oct 13, 2026
View reviewed changes

@Byron Byron left a comment

Copy link
Copy Markdown

There was a problem hiding this comment.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

I wonder if this is the same as what would happen if I had updated the advisory myself?
Sometimes advisory authors ask me to make changes, but it seems like this is what they can do as well.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.
ranjiGT reacted with heart emoji
All reactions
  • ❤️ 1 reaction
@ranjiGT

ranjiGT commented Oct 13, 2026

Copy link
Copy Markdown
Author

Thanks, @Byron, for reviewing and approving the changes!

That's an interesting point. My understanding is that contributions through github/advisory-database allow community members to propose improvements to existing advisories, while advisory authors may also be able to update their own advisories directly.

I'm not entirely sure whether both workflows ultimately follow the same review and publishing process.

I appreciate your feedback and approval!
All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.
@advisory-database
advisory-database Bot merged commit cd9d369 into ranjiGT/advisory-improvement-10326 Oct 19, 2026
6 checks passed

Uh oh!

There was an error while loading. Please reload this page.
@advisory-database

advisory-database Bot commented Oct 19, 2026

Copy link
Copy Markdown
Contributor

Hi @ranjiGT! Thank you so much for contributing to the GitHub Advisory Database. This database is free, open, and accessible to all, and it's people like you who make it great. Thanks for choosing to help others. We hope you send in more contributions in the future!
ranjiGT reacted with heart emoji
All reactions
  • ❤️ 1 reaction

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.
@advisory-database
advisory-database Bot deleted the ranjiGT-GHSA-3rp5-jjmw-4wv2 branch October 19, 2026 20:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

Copilot code review Copilot
Copilot review effort
Applies to this pull request for everyone.Learn more about Copilot code review.
Copilot left review comments
+1 more reviewer
@Byron Byron Byron approved these changes
Reviewers whose approvals may not affect merge requirements

Uh oh!

There was an error while loading. Please reload this page.

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Uh oh!

There was an error while loading. Please reload this page.

4 participants

@ranjiGT @github @Byron
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
You are visitor 01402520 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.