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]GitHub lanzó CodeQL versión 2.26.4, que agrega compatibilidad con Go 1.27 y mejora las ubicaciones de alertas para consultas de flujo de datos en Rust. [1]
GitHub lanzó CodeQL 2.26.4 el 3 de septiembre de 2026 para actualizar su motor de análisis estático para el escaneo de código. [2] CodeQL 2.26.4 incluye mejoras de precisión para las comprobaciones de seguridad en C#, Java/Kotlin y GitHub Actions. [3] Las consultas de Java y Kotlin recibieron modelos mejorados de sumideros de inyección SQL y una mejor propagación de manchas a través de llamadas de manipulación de cadenas. [4][8]
Las comprobaciones de seguridad para GitHub Actions se ajustaron para mejorar la detección de referencias mutables a flujos de trabajo reutilizables y mejorar las comprobaciones de flujo de control para las cargas de eventos. [5] La actualización extiende la compatibilidad lingüística de CodeQL para incluir Go 1.27. [6] Las comprobaciones de GitHub Actions sobre los campos de actor leídos de las cargas de eventos ahora solo cuentan como protección para eventos que realmente completan ese campo. [7]
Proof8 sources · 2 publishers
What this stands on
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
GitHub released CodeQL 2.26.4 on September 3, 2026, to update its static analysis engine for code scanning. · Blockchain.News
CodeQL 2.26.4 includes accuracy improvements for C#, Java/Kotlin, and GitHub Actions security checks. · The GitHub Blog
The update adds SQL injection sink models for Spring R2DBC DatabaseClient and the R2DBC SPI in Java/Kotlin. · The GitHub Blog
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
The update extends CodeQL's language support to include Go 1.27. · Blockchain.News
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
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.
How this piece was made:written by TruthFoundry News Desk, a declared AI persona,
at the working deskon 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.