EM-20261112-HUN9
VulnerabilityMedium severity
Git Vulnerability (CVE-2026-113408)
CVE-2026-113408
Status
Developing
Since : signals keep joining.
- First Signal
- Nov 10 18:00 UTCC41 Red Hat Security Data
- Page Born
- Nov 12 09:32 UTCsecond source joined
- Last Signal
- Nov 12 09:32 UTC11 hours before snapshot
- Sources
- 21 official · 1 research, news or crowd
- Open For
- 40 hoursso far
Life Of This Page
- 1BornA second, independent source names it.
- 2Developing · NowNew signals join; severity can move.
- 3ConfirmedNot yetCISA KEV lists it, or exploitation in the wild is reported.
- 4ResolvedNot yetPast the fix deadline and 14 days with no new signal.
- 5ArchivedNot yet30 days after resolved. Read only; the link keeps working. Reopens if it comes back.
The ID never changes, and earlier addresses keep working. A correction is logged, never overwritten. If two pages turn out to be one incident, the later one points to the earlier.
Vulnerability Lifecycle
- Disclosed: reachedNov 12 07:16 UTCC6 NVD published
- Scored: reachedNov 12 07:16 UTCCVSS 3.3
- Exploited: not yetNot yetNo exploitation reported
- Advisories: not yetNot yetNone yet
- Vendor Response: reachedNov 10 18:00 UTCC41 published
- Resolved: not yetNot yetAfter 14 quiet days
Timeline
Point at a mark to read it. Squares are signals, colored by severity; every one is also listed under Signals.
Signals
- GHSA-64xm-x3j2-5g2g / CVE-2026-113408 (opens source in a new tab) Path traversal in Git allows writing to arbitrary file via cloning and committing to bad repository Med severityDatabaseC29 CIRCL Vulnerability-Lookup
- Red Hat: CVE-2026-113408 (moderate) (opens source in a new tab) git: git: Unintended file writes via malformed unborn HEAD advertisement Med severityVendorC41 Red Hat Security Data