steveukx
git-js
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-js, 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-2026-102829 | 29 Sep 2026 | git-js: < 2.0.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-102828 | 29 Sep 2026 | git-js: >= 3.15.0, < 4.0.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-102827 | 29 Sep 2026 | git-js: < 4.0.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-102826 | 29 Sep 2026 | git-js: < 4.0.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-28291 | 13 Apr 2026 | < 3.32.0 | 3.32.0. | Update reference ↗ |
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.