Code scanning AI Scan enablement status in security overview
Organization and enterprise administrators can now see AI Scan for pull requests enablement status in the security overview coverage view. The code scanning summary shows enabled and not enabled repository counts, while repository rows show each repository’s effective AI Scan enablement.
Also shipped Oct 6, 2026GitHub in October 2026 →
WAF Release - 2026-10-06
This release introduces a new detection to mitigate a heap-based buffer overflow vulnerability in F5 BIG-IP, and enhances existing command injection protections by incorporating tested beta logic into the baseline rule. Key Findings CVE-2026-94127: A heap-based buffer overflow vulnerability in F5 BIG-IP.
Metric view window measures are generally available
Window measures in metric views are now generally available. Window measures define rolling window, cumulative, or semiadditive aggregations, such as moving averages, period-over-period changes, and running totals. See Window measures .
Conversational analytics in BigQuery now supports the AI.CAUSAL_EFFECT function to quantify the impact of...
Conversational analytics in BigQuery now supports the AI.CAUSAL_EFFECT function to quantify the impact of specific interventions on time series data. This feature is in Preview .
Gemini Enterprise: Control access to Antigravity features
Administrators can control whether users in their organization have access to the following Google Antigravity features: Boost : Uses a tiered multi-agent hierarchy to solve complex algorithmic challenges and deep debugging tasks with the /boost command. This feature is generally available (GA) in Antigravity.
Gemini Nano Banana 2.1
Gemini Nano Banana 2.1 ( gemini-nano-banana-2.1 ) is available in General Availability (GA) . Gemini Nano Banana 2.1 is optimized for high-speed multimodal image generation and editing, offering improved visual quality, prompt adherence, and text rendering across 1K , 2K , and 4K output resolutions.
Genie Code CLI is in Beta
Genie Code CLI is a coding agent that runs in your terminal, tuned for data and AI work on Databricks. It works with your local files and uses the Databricks CLI to discover data, answer questions, and build and deploy assets such as pipelines, models, and apps. Model access is provided and governed through Unity Gateway. See Genie Code CLI .
More from GitHub Advanced SecurityEvery GitHub Advanced Security release →
Secret scanning adds detectors for Lovable, Supabase, and more
Secret scanning now detects new secret types from Lovable Labs, Pydantic Services Inc., and Supabase. New secret scanning partner The following provider joined the secret scanning partnership program.
CodeQL 2.27.2 improves C++, Go, Rust, and JavaScript analysis
CodeQL 2.27.2 is now available, adding a C++ regular-expression parser and analysis improvements across several languages. CodeQL is the static analysis engine behind GitHub code scanning, which helps you find and remediate security issues in your code. The Default suite runs 498 security queries covering 170 CWEs.
New fields for SecurityAdvisory GraphQL API
You can now read more of the GitHub Advisory Database directly from the GraphQL API without falling back to the REST API. The SecurityAdvisory object gained five new fields: cveId : The advisory’s CVE identifier. sourceCodeLocation : A link to the affected source code relevant to the advisory. githubReviewedAt : When GitHub reviewed the advisory.
Confidential comments on repository security advisories
You can now post confidential comments on repository security advisories. Confidential comments are visible only to people with write access to the repository, so you can discuss a report with your team without the reporter or other invited collaborators seeing it.
Repository security advisory comments API in public preview
You can now read, add, and edit comments on repository security advisories using the REST API, including advisories created from private vulnerability reports. Until now, the discussion on an advisory was only reachable in the web UI, even though it often holds the most useful triage context on a vulnerability report.
Unvalidated npm trusted publishing configurations now expire
Unvalidated npm trusted publishing configurations now expire 48 hours after creation and can no longer authorize publishing. This limits the risk of trusting a repository or project name that changes ownership. Your configuration becomes validated and exempt from expiry after its first successful publish.
npm staged publishing now supports creating new packages
You can now create a new npm package with npm stage publish , using a local session or a granular access token, including a stage-only token. This lets you create packages from your automated workflows without a manual first publish. This works for public scoped and unscoped packages, and private scoped packages.
Rate limits for private vulnerability reports
Open source maintainers are receiving more low-quality and automated vulnerability reports, which can bury the reports that matter. Rate limits cap how many new reports a single account can submit in a day, both to your repository and across GitHub. This helps protect you from bulk and automated submissions, while legitimate researchers can still reach you.