j6t
git-gui
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
Official registry publication history is available at git-gui, but registry activity is not a publisher support boundary.
A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.
CVE-observed version history
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2025-46835 | 10 Jul 2025 | < 2.43.7; >= 2.44.0, < 2.44.4; >= 2.45.0, < 2.45.4; >= 2.46.0, < 2.46.4; >= 2.47.0, < 2.47.3; >= 2.48.0, < 2.48.2; >= 2.49.0, < 2.49.1; >= 2.50.0, < 2.50.1 | For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2025-46334 | 10 Jul 2025 | < 2.43.7; >= 2.44.0, < 2.44.4; >= 2.45.0, < 2.45.4; >= 2.46.0, < 2.46.4; >= 2.47.0, < 2.47.3; >= 2.48.0, < 2.48.2; >= 2.49.0, < 2.49.1; >= 2.50.0, < 2.50.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
How this record is maintained
The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.