GitHub Bolsters Code Security with AI-Powered Vulnerability Detection
**GitHub** is integrating AI-based scanning into its Code Security tool to expand vulnerability detection capabilities. This new approach complements the existing **CodeQL** static analysis, aiming to cover more languages and frameworks, particularly those challenging for traditional methods.

**GitHub** is adopting AI-based scanning for its Code Security tool to expand vulnerability detections beyond the **CodeQL** static analysis and cover more languages and frameworks.
The developer collaboration platform says that the move is meant to uncover security issues "in areas that are difficult to support with traditional static analysis alone."
**CodeQL** will continue to provide deep semantic analysis for supported languages, while AI detections will provide broader coverage for Shell/Bash, Dockerfiles, Terraform, PHP, and other ecosystems.
The new hybrid model is expected to enter public preview in early Q2 2026, possibly as soon as next month.
### Finding Bugs Before They Bite
**GitHub** Code Security is a [set of application security tools](https://github.com/security/advanced-security/code-security) integrated directly into **GitHub** repositories and workflows.
It is available for free (with limitations) for all public repositories. However, paying users can access the [full set of features](https://github.com/security/plans) for private/internal repositories as part of the **GitHub** Advanced Security (**GHAS**) add-on suite.
It offers code scanning for known vulnerabilities, dependency scanning to pinpoint vulnerable open-source libraries, secrets scanning to uncover leaked credentials on public assets, and provides security alerts with Copilot-powered remediation suggestions.
The security tools operate at the pull request level, with the platform selecting the appropriate tool (**CodeQL** or AI) for each case, so any issues are caught before merging the potentially problematic code.
If any issues, such as weak cryptography, misconfigurations, or insecure SQL, are detected, those are presented directly in the pull request.
**GitHubβs** internal testing showed that the system processed over 170,000 findings over 30 days, resulting in 80% positive developer feedback, and indicating that the flagged issues were valid.
These [results showed βstrong coverageβ](https://github.blog/security/application-security/github-expands-application-security-coverage-with-ai-powered-detections/) of the target ecosystems that had not been sufficiently scrutinized before.
**GitHub** also highlights the importance of Copilot Autofix, which suggests solutions for the problems detected through **GitHub** Code Security.
Stats from 2025 comprising over 460,000 security alerts handled by Autofix show that resolution was reached in 0.66 hours on average, compared to 1.29 hours when Autofix wasnβt used.
**GitHubβs** adoption of AI-powered vulnerability detection marks a broader shift where security is becoming AI-augmented and also natively embedded within the development workflow itself.
<div>
<a rel="noopener sponsored" href="https://hubs.li/Q043YRMg0"><img alt="tines" src="https://www.bleepstatic.com/c/p/red-report.jpg"></a>
<div>
<h2><a rel="noopener sponsored" href="https://hubs.li/Q043YRMg0">Red Report 2026: Why Ransomware Encryption Dropped 38%</a></h2>
<p>Malware is getting smarter. The Red Report 2026 reveals how new threats use math to detect sandboxes and hide in plain sight.</p>
<p>Download our analysis of 1.1 million malicious samples to uncover the top 10 techniques and see if your security stack is blinded.</p>
</div>
</div>