Evaluating ChatGPT for Software Vulnerability Tasks: A Comparative Analysis

With its impressive 1.7 trillion parameters, ChatGPT has emerged as a powerful language model. However, its applicability to code-oriented tasks, such as software vulnerability analysis and repair, remains relatively unexplored. In this article, we delve into the evaluation of ChatGPT against code-specific models, specifically examining its performance on four vulnerability tasks using the Big-Vul and CVEFixes datasets. This comprehensive analysis sheds light on the potential limitations of using ChatGPT for software vulnerability tasks while emphasizing the need for domain-specific fine-tuning.

Evaluation of ChatGPT against code-specific models

To comprehensively evaluate ChatGPT’s performance, security analysts conducted experiments using the Big-Vul and CVEFixes datasets. These datasets provide a comprehensive set of vulnerability tasks, enabling a thorough comparison of ChatGPT against baseline methods. The evaluation focused on the F1-measure and top-10 accuracy metrics.

The results of the evaluation revealed that ChatGPT achieved an F1-measure of 10% and 29% on the Big-Vul and CVEFixes datasets, respectively. These scores were significantly lower compared to the other baseline methods. Similarly, the top-10 accuracy of ChatGPT was 25% and 65%, which again reflected the lowest performance among the examined models.

Analysis of Multiclass Accuracy

In addition to F1-measure and top-10 accuracy, multiclass accuracy was also considered as a crucial performance indicator. The analysis revealed that ChatGPT achieved the lowest multiclass accuracy of 13%, showcasing a striking 45%-52% difference from the best baseline model. These outcomes underscore the challenges faced by ChatGPT in accurately classifying vulnerability tasks across multiple classes.

Evaluation of Severity Estimation

Severity estimation holds paramount importance in vulnerability analysis to prioritize remediation efforts. However, ChatGPT’s performance in this regard proved to be unsatisfactory. The evaluation indicated that ChatGPT exhibited the highest mean squared error (MSE) of 5.4 and 5.85, implying its inaccurate severity estimation compared to the other baselines. This finding raises concerns about relying on ChatGPT for precise severity estimation in vulnerability assessment.

Assessment of Repair Patch Generation

One vital aspect of vulnerability repair is the generation of correct repair patches. Regrettably, ChatGPT failed to generate accurate repair patches in this evaluation. On the other hand, the baseline models demonstrated success in rectifying vulnerable functions, correctly repairing 7% to 30% of them. This stark contrast highlights the limitations of ChatGPT in generating effective repair solutions.

Limitations of fine-tuning

Fine-tuning is a commonly employed technique to optimize language models for specific tasks. However, in the case of ChatGPT, fine-tuning for vulnerability tasks is not viable due to proprietary parameters. This constraint further underlines the challenges in adapting ChatGPT directly for software vulnerability tasks.

The Importance of Domain-specific Fine-tuning

The analysis of ChatGPT’s performance in vulnerability tasks underscores the significance of domain-specific fine-tuning. The complexity and specificity of software vulnerability tasks necessitate the customization of language models like ChatGPT to better suit the requirements. This suggests the need for further research and work on fine-tuning or adapting ChatGPT specifically for software vulnerability tasks.

Comparison with previous studies

While previous studies have examined the effectiveness of large language models in automated program repair, they have not accounted for the latest versions of ChatGPT. This article bridges that gap by shedding light on the specific performance of ChatGPT in software vulnerability tasks. Additionally, the notable disparities in results indicate the necessity for dedicated exploration of ChatGPT’s potential in this domain.

In conclusion, the evaluation of ChatGPT for software vulnerability tasks reveals its limitations in comparison to code-specific models. The lower F1-measure, top-10 accuracy, multiclass accuracy, inaccurate severity estimation, and inability to generate correct repair patches highlight the challenges faced by ChatGPT in this context. The proprietary nature of its parameters further restricts fine-tuning for vulnerability tasks. As such, this study emphasizes the need for additional research and efforts to fine-tune or tailor ChatGPT specifically for software vulnerability analysis and repair. By addressing these challenges, ChatGPT could potentially be leveraged more effectively in securing software systems in the future.

Explore more

How Companies Can Fix the 2026 AI Customer Experience Crisis

The frustration of spending twenty minutes trapped in a digital labyrinth only to have a chatbot claim it does not understand basic English has become the defining failure of modern corporate strategy. When a customer navigates a complex self-service menu only to be told the system lacks the capacity to assist, the immediate consequence is not merely annoyance; it is

Customer Experience Must Shift From Philosophy to Operations

The decorative posters that once adorned corporate hallways with platitudes about customer-centricity are finally being replaced by the cold, hard reality of operational spreadsheets and real-time performance data. This paradox suggests a grim reality for modern business leaders: the traditional approach to customer experience isn’t just stalled; it is actively failing to meet the demands of a high-stakes economy. Organizations

Strategies and Tools for the 2026 DevSecOps Landscape

The persistent tension between rapid software deployment and the necessity for impenetrable security protocols has fundamentally reshaped how digital architectures are constructed and maintained within the contemporary technological environment. As organizations grapple with the reality of constant delivery cycles, the old ways of protecting data and infrastructure are proving insufficient. In the current era, where the gap between code commit

Observability Transforms Continuous Testing in Cloud DevOps

Software engineering teams often wake up to the harsh reality that a pristine green dashboard in the staging environment offers zero protection against a catastrophic failure in the live production cloud. This disconnect represents a fundamental shift in the digital landscape where the “it worked in staging” excuse has become a relic of a simpler era. Despite a suite of

The Shift From Account-Based to Agent-Based Marketing

Modern B2B procurement cycles are no longer initiated by human executives browsing LinkedIn or attending trade shows but by autonomous digital researchers that process millions of data points in seconds. These digital intermediaries act as tireless gatekeepers, sifting through white papers, technical documentation, and peer reviews long before a human decision-maker ever sees a branded slide deck. The transition from