TraceVIC: Causal Reasoning over Code Evolution for Identifying Vulnerability-Inducing Commits
Software vulnerabilities are often discovered long after they are introduced, making it difficult to identify the vulnerability-inducing commit (VIC) responsible for introducing the underlying vulnerable condition. Existing VIC identification techniques largely rely on git blame to trace vulnerable code through revision history and use positional heuristics, such as selecting its earliest or most recent modification. However, the true VIC may occur anywhere within this history, and vulnerable behavior may depend on code that evolves across multiple revisions. We therefore argue that VIC identification requires reasoning about how vulnerability-relevant code evolves, rather than simply whe...
| Authors | Fnu Tanish, Samiha Shimmi, Samikshya Chapagain et al. |
|---|---|
| Primary category | cs.SE |
| Published | 22 September 2026 |
| Last updated at source | 4 October 2026 |
Silytics shows public metadata from arXiv and links to the original. Information may be incomplete or out of date. Last refreshed 17 October 2026. Licenses and terms of the original apply to the work itself. Not financial, legal or professional advice.