GitHub announced CodeQL 2.27.4 on November 4, 2026, a maintenance release of the static analysis engine that powers code scanning. The update sharpens several queries for Java, Kotlin, Rust and C/C++, retags a group of regular expression queries, and adds a symlink safety check when packs are bundled or published.
The release arrives only a day after GitHub described version 2.27.3 in its changelog, so teams on github.com get both sets of changes almost back to back. For most users nothing needs to be done, but anyone who runs the CLI in their own pipelines or filters alerts by CWE should look at the details.
What changed in the queries
Most of the work in this version goes into accuracy. Fewer noisy alerts mean developers spend less time closing results that were never real problems, and they are more likely to trust the ones that remain.
- Java and Kotlin: the log injection query understands more sanitizers and guard checks drawn from Guava, the JDK, Apache Commons Lang and Text, the OWASP Java Encoder and Spring. Path injection checks also accept more substring guards and string replace or remove calls from Commons Lang and Guava.
- Rust: false positives drop in the uncontrolled allocation size, log injection and cleartext logging queries. One fix stops the value unwrapped by the question mark operator from being treated as leaving the function on an early return. New neutral models also cover certain actix-web request helpers and common Vec and VecDeque methods.
- C/C++: the suspicious pointer scaling query now leaves deliberate arithmetic on std::byte* buffers alone. The unused local and unused static variable queries skip anything tagged [[maybe_unused]], the attribute added in C++17.
- JavaScript/TypeScript: computed __proto__ properties in object literals no longer trigger the invalid prototype value query. Taint tracking now follows trimStart, trimEnd and normalize, and a flow summary bug in Array.prototype.flatMap is fixed.
CWE-730 removed from regex queries
CodeQL has taken the CWE-730 tag off its ReDoS and regex injection queries in C#, Java/Kotlin, JavaScript/TypeScript, Python, Ruby and Swift. The JavaScript list also includes the server crash and loop bound injection queries. According to the full changelog, MITRE no longer allows CWE-730 to be used when mapping vulnerabilities.
The queries keep every other CWE tag they had, and the detection logic itself does not change. GitHub credits a community issue on the CodeQL repository for raising the problem.
For C and C++ there is also a new cpp-code-quality suite. It groups queries aimed at maintainability and reliability issues rather than security bugs.
CLI and library changes
Two CLI fixes matter for automation. Java virtual machine warnings and startup errors now go to standard error instead of standard output, so commands that print JSON no longer risk producing broken output.
When running codeql pack bundle or codeql pack publish, the CLI resolves symbolic links and drops any file that ends up outside the pack root, printing a warning when it does.
There are a few library level changes as well:
- The JavaScript/TypeScript extractor ignores the SEMMLE_TYPESCRIPT_HOME variable and sticks to the TypeScript compiler shipped inside CodeQL. This is listed as a breaking change.
- The Go extractor stops editing the global Git configuration when private registries are set, and passes the proxy certificate through GIT_SSL_CAINFO instead.
- The Go library deprecates ControlFlow::ConditionGuardNode in favor of the shared guards library.
- C# reverts an earlier tweak that passed proxy and certificate settings to the NuGet process, since they were not always honored.
According to the changelog, the default suite now runs 498 security queries covering 169 CWEs, and the extended suite adds 131 more.
What it means for developers
If you use default code scanning on github.com, expect some existing alerts to close on their own during the next analysis, mainly in Rust, Java and C++ projects. That is the accuracy work taking effect, not a sign that something broke. Check that the closed alerts match code you already knew was safe.
Teams that build dashboards, compliance reports or alert rules on CWE numbers should search for CWE-730 now. Regex denial of service findings will no longer carry that tag, so a filter keyed on it may quietly stop matching. Switch such filters to the remaining tags or to the query IDs themselves.
If any build script sets SEMMLE_TYPESCRIPT_HOME to pin a TypeScript version, remove it, because the extractor ignores it from this release.
Pack authors who rely on symlinks to shared files should also confirm their published archives still contain everything they expect. For more context on recent GitHub security tooling, see our coverage of CodeQL 2.27.3 and the Dependabot reachability analysis preview.
How to upgrade
GitHub rolls out each CodeQL version to code scanning on github.com automatically, so cloud users get 2.27.4 without action. The changes will ship with GitHub Enterprise Server 3.24. Administrators on older Enterprise Server versions can update the CodeQL bundle by hand, and anyone running the standalone CLI should download the new release.
Conclusion
CodeQL 2.27.4 is a quiet but useful release. It removes a range of false positives, follows MITRE guidance on CWE-730, makes CLI output safer for scripts and closes a symlink gap in pack publishing. Review any CWE based filters and TypeScript environment settings, then let the update run.
Sources
- GitHub Changelog: CodeQL 2.27.4 improves accuracy and query metadata
- CodeQL documentation: CodeQL 2.27.4 changelog
See my articles more often when you search Google.
