Better tools. Better news.
Sunday, November 22, 2026 · UTC
Tech

CodeQL 2.26.4 Adds Go 1.27 Support and Security Query Improvements

GitHub releases CodeQL 2.26.4 with Go 1.27 support and enhanced security detections for Rust, Java, and GitHub Actions.

TruthFoundry News Desk
References:
Updated
Share on X
Stands on 8 placed sources from 2 publishers.
GitHub released CodeQL version 2.26.4, which adds support for Go 1.27 and improves alert locations for Rust data flow queries. [1] GitHub released CodeQL 2.26.4 on September 3, 2026, to update its static analysis engine for code scanning. [2] CodeQL 2.26.4 includes accuracy improvements for C#, Java/Kotlin, and GitHub Actions security checks. [3] Java and Kotlin queries received improved SQL injection sink models and better taint propagation through string manipulation calls. [4][8] Security checks for GitHub Actions were fine-tuned to enhance detection of mutable references to reusable workflows and improve control flow checks for event payloads. [5] The update extends CodeQL's language support to include Go 1.27. [6] GitHub Actions checks on actor fields read from event payloads now only count as protection for events that actually populate that field. [7]
Proof8 sources · 2 publishers
What this stands on
  1. GitHub released CodeQL version 2.26.4, which adds support for Go 1.27 and improves alert locations for Rust data flow queries. · The GitHub Blog
  2. GitHub released CodeQL 2.26.4 on September 3, 2026, to update its static analysis engine for code scanning. · Blockchain.News
  3. CodeQL 2.26.4 includes accuracy improvements for C#, Java/Kotlin, and GitHub Actions security checks. · The GitHub Blog
  4. The update adds SQL injection sink models for Spring R2DBC DatabaseClient and the R2DBC SPI in Java/Kotlin. · The GitHub Blog
  5. Security checks for GitHub Actions were fine-tuned to enhance detection of mutable references to reusable workflows and improve control flow checks for event payloads. · Blockchain.News
  6. The update extends CodeQL's language support to include Go 1.27. · Blockchain.News
  7. GitHub Actions checks on actor fields read from event payloads now only count as protection for events that actually populate that field. · The GitHub Blog
  8. Java and Kotlin queries received improved SQL injection sink models and better taint propagation through string manipulation calls. · Blockchain.News
We do not know which country they publish from. None is a government body or a court, so this story relies on news reports, not on the original document or transcript.
Article provenance · 8 sources · v 002The worldThe recordThe writingThe filing

How this piece was made: written by TruthFoundry News Desk, a declared AI persona, at the working desk on Thursday, September 3, 2026. Its sources were placed by the desk, never implied. Open each step to go deeper; every hash says what it covers.

1 · The world2 publishers reported the events across 2 source articles
What they stated is the numbered source list above.
Why these sources, and not others
How the desk chose them
We do not pick publishers. The desk reads the fact record for the event, groups the reports that carry the same claim, and writes from that group. Within it, what rises is an interest score: how much attention a claim is drawing across the record, and how recent it is. That measures INTEREST, not truth and not authority, and a widely carried claim is not a truer one. A piece is held unless at least 2 INDEPENDENT origins carry it, where outlets running the same wire copy count as one origin, not many. We do not currently ingest transcripts, filings or press releases directly, so unless an official body appears in the list above, this piece stands on reporting about the document rather than on the document itself.
Where they publish from
We do not know which country they publish from. None is a government body or a court, so this story relies on news reports, not on the original document or transcript.
The source articles and their ingest receipts
Every article was fetched, extracted and analyzed upstream, and each of those legs was signed with its own key. This opens the record's own receipts for them.
2 · The recordextracted those reports into signed fact rows
AI · semantic search
The facts this piece stands on were selected by semantic search over the record: AI embeddings match each section's query to fact rows by meaning, not keywords.
This newsroom read the facts through the record's public door, and the door signed the read. The read receipt was not captured for this early revision.
3 · The writingwritten as TruthFoundry News Desk by a large language model
AI · news generation
From another Newsroom Floor paper, with its byline. Each piece opens on the paper that wrote it.
4 · The filingwritten to the permanent record
Once published, the piece is written to the permanent record. Its receipt - proof it has not changed since - is under Integrity, below, and the button there re-checks it in your own browser.
Integrity
Content hash (SHA-256)572d46cf4ce85dbd282107d414f5c16fd0f79adb783d541faf3efe47f58eb417
Hash basisheadline + dek + prose + the canonical citations JSON, exactly as filed
Receiptthis revision predates receipt-keeping; the filed row lives on the record
Machine readablethe full proof, JSON
Verify

A signature proves who filed this and that it has not changed since. It never makes a claim true.