Security advisory: critical PHP and Node.js vulnerabilities are being exploited in the wild. What you need to do →
All months

Radar · 2026-07

July 2026

PSPF Release 2026 makes post-quantum transition planning mandatory, an nginx flaw rated major can crash workers and may allow code execution, Node.js patches eleven vulnerabilities across all release lines, npm begins scanning packages at publish time and Drupal AI restructures its governance.

What's on our radar this month: releases, advisories and standards across the stack we run and the platforms we integrate with.

AI platform and models

Sections
  • notable MCP

    MCP 2026-07-28 specification goes stateless — blog.modelcontextprotocol.io

    The final Model Context Protocol 2026-07-28 specification shipped on 28 July 2026. The core protocol is now fully stateless — the initialize handshake and protocol-level sessions are gone — with new Mcp-Method and Mcp-Name HTTP headers for gateway routing, cacheable list results, and multi round-trip requests replacing server-initiated ones. Dynamic Client Registration, the HTTP+SSE transport and the Roots, Sampling and Logging features are deprecated, and the Tier 1 SDKs shipped support on day one.

    Teams running MCP servers should plan the upgrade within the minimum twelve-month window for the deprecated features, and note that the stateless core and routing headers change how MCP traffic can be cached and load-balanced at the edge.

  • notable AI security

    Hidden PR comments can hijack AI code-review agents via Azure DevOps MCP server — thehackernews.com

    Research reported on 22 July 2026 showed that Microsoft's Azure DevOps MCP server returns pull-request descriptions without the prompt-injection guardrail its wiki and build-log tools apply. Instructions planted in HTML comments — invisible in the web UI — can redirect a reviewer's AI agent to exfiltrate source code, secrets and work items using the reviewer's own credentials. No fix or CVE existed as of late July.

    If AI agents review pull requests in your pipelines, scope their tokens to least privilege, restrict which MCP tools and domains they can reach, and keep a human approval gate on anything the agent proposes.

  • fyi Anthropic

    Anthropic releases Claude Opus 5 — anthropic.com

    Released on 24 July, Opus 5 is designed for everyday use and sets new highs on coding and knowledge-work evaluations, coming close to the frontier Fable 5 model at half the price, with a selectable effort setting for trading capability against token spend. Pricing is unchanged from Opus 4.8, and in Claude.ai, Claude Code and Cowork, requests flagged by its cyber safeguards fall back to Opus 4.8 by default, a fallback that can also be enabled on the API.

    Benchmark existing prompts before switching defaults, and check availability in your region and platform before assuming data residency carries over to the new model.

Security and edge

Sections
  • critical nginx

    nginx flaw rated major can crash workers and may allow code execution — thehackernews.com

    CVE-2026-42533, patched on 15 July in nginx 1.30.4 and 1.31.3, is a heap buffer overflow triggered when regex captures and map variables interact — a regex-based map whose output is used in a string expression after an earlier capture. nginx's own register rates the flaw major and lists every version from 0.9.6 to 1.31.2 as vulnerable. Crafted requests can crash worker processes, F5 says the flaw may allow remote code execution where ASLR is disabled or can be bypassed, and a full proof-of-concept exploit was released on 28 July.

    Upgrade to 1.30.4 or 1.31.3 as a priority if your configuration combines map with regular expressions — and patch regardless, since configurations drift.

  • notable Browsers

    Critical Firefox and Chrome fixes land on the same day — thehackernews.com

    Mid-July browser updates carried unusually serious fixes, both landing on 14 July. Firefox 152.0.6 patches CVE-2026-15718, an invalid-pointer flaw in the JavaScript WebAssembly component, and CVE-2026-15719, a site isolation flaw in the DOM navigation component. Mozilla rates both Critical and says exploit code is public for each. Chrome 150.0.7871.124/.125 fixes fifteen flaws including two Google-rated Critical use-after-free bugs in Ozone. Mozilla says it is not aware of any in-the-wild attacks on either Firefox flaw; Google made no exploitation statement either way.

    Managed browser fleets should take the July updates promptly. Mozilla's own note that exploit code is public, with no in-the-wild attacks it knows of, is the whole argument for moving on the Firefox flaws before that changes rather than after.

  • fyi TLS

    CA/Browser Forum strips redundant EV validity and reuse rules — cabforum.org

    CA/Browser Forum ballot SC102 passed unanimously on 14 July 2026. It drops the extra registrant re-check from EV domain validation reuse and replaces the EV-specific validity and reuse wording with references to the Baseline Requirements. The sponsors say EV certificates were already bound by those limits, so the ballot imposes no new obligation and has no effective date.

    Fold EV renewals into the same automation as everything else. EV certificates already expire on the same shrinking schedule as every other public TLS certificate, and this ballot removes the text that suggested otherwise.

Standards and compliance

Sections
  • critical PSPF

    PSPF Release 2026 lands with mandatory post-quantum transition plans — protectivesecurity.gov.au

    The annual Protective Security Policy Framework release took effect on 1 July 2026. Entities must now maintain post-quantum cryptography transition plans and require PQC algorithm support in newly procured equipment, apply the Commonwealth Technology Standard when authorising systems up to SECRET, and meet updated hosting and gateway requirements, including those under the Gateway Security Standard introduced in PSPF Release 2025.

    Commonwealth entities and their web and hosting suppliers should map the 2026 changes — the post-quantum transition planning requirement in particular reaches into TLS and infrastructure roadmaps for government sites.

  • notable ASD

    ASD co-releases the 2026 minimum elements for software bills of materials — cyber.gov.au

    On 29 July 2026 CISA, the NSA, FBI and international partners including ASD's ACSC released the 2026 Minimum Elements for a Software Bill of Materials, superseding the 2021 NTIA baseline. The update adds ten data fields, including SBOM author signature, tool name and generation context, and component hash and licence. It requires every component including transitive dependencies, with no minimum depth, names SPDX and CycloneDX as the widely used formats, asks organisations to accept any widely used machine-processable format and drops SWID tags.

    Teams generating SBOMs in CI should regenerate against the 2026 elements and check their tooling emits the new fields — agencies will reference this baseline when requesting SBOMs from suppliers.

  • notable Privacy Act

    OAIC updates facial recognition guidance after the Bunnings ruling — oaic.gov.au

    On 29 July 2026 the Privacy Commissioner published updated guidance on facial recognition technology in retail and other high-volume public spaces, implementing the Administrative Review Tribunal's February 2026 decision in the Bunnings matter. It clarifies how the consent exceptions for collecting biometric information apply and states that Australian law requires a precautionary approach to the technology; the parallel Kmart matter remains before the tribunal, with hearings scheduled for early 2027.

    Any organisation weighing biometric capability — including camera-linked kiosk or web features — should run the guidance's necessity and proportionality analysis per deployment before collecting anything.

CMS and platforms

Sections
  • notable Drupal

    Drupal 11.4.0 ships with major performance gains and a new core CLI — drupal.org

    Drupal 11.4.0 landed on 1 July 2026, a short slip from the planned week of 22 June after security and dependency patch releases consumed release-manager time. On a cold cache, Drupal 11.4 performs just over a third of the database and cache lookups of Drupal 11.0 and 10.6, Brotli support delivers 15–25 per cent better compression than gzip on aggregated JavaScript and CSS, recipe-based site installation is twice as fast, and a new extensible native CLI (./vendor/bin/dr) arrives with the stated aim of gradually replacing Drush. The Gin admin theme also ships as a new experimental theme named Default Admin, which will replace Claro once stable.

    Schedule the 11.4 upgrade — the lookup and compression improvements translate directly into faster page delivery — and start trialling the new CLI in build tooling before Drush assumptions harden further.

  • fyi Drupal

    Drupal AI reorganises: Inside AI, Outside AI and three-tier governance — drupal.org

    Two mid-year posts set the Drupal AI Initiative's shape for what comes next. On 25 June, execution split into two workstreams: Inside AI (assistants, in-product workflows and page building within the Drupal interface) and Outside AI (making Drupal the platform external AI agents connect to, inspect and act on), the latter targeting a first proof of direction at DrupalCon Rotterdam. On 9 July, governance moved to three tiers — an AI Board formed from the founding partners, a leadership team of functional and cross-functional leads, and a community of 30-plus AI partner organisations.

    If your roadmap includes agent access to CMS content, follow the Outside AI stream — its choices will shape how external agents interact with Drupal sites, and it is the CMS world's clearest answer yet to agent-driven traffic.

  • fyi WordPress

    WordPress 7.0.1 lands, and Gutenberg opens a React 19 test flag — developer.wordpress.org

    WordPress 7.0.1 arrived on 9 July and bundles 13 Core tickets and 13 Gutenberg fixes. 7.1 Beta 1 is scheduled for 15 July, with a final release on 19 August. The Abilities API shipped as infrastructure in WordPress 6.9; a merge proposal would add read-only core abilities for settings, content and users. Gutenberg 23.4 ships an experimental gutenberg-react-19 flag so plugins can test React 19 before Core makes that jump.

    Apply 7.0.1, then test plugins and editor customisations against the 7.1 betas and the experimental React 19 flag.

Supply chain, CI/CD and IaC

Sections
  • notable npm

    npm scans packages at publish time; Actions holds suspicious workflows — github.blog

    Two 28 July changes push GitHub's supply chain defences earlier in the attack chain. Newly published npm packages are now scanned automatically before they become installable — released as normal, held for manual review or blocked — adding a delay of around five minutes between publish and availability. On public repositories on github.com, GitHub Actions now holds workflow runs it identifies as potentially malicious until a collaborator with write access approves them, targeting attacks that use compromised credentials to push malicious workflows.

    If your release automation assumes a package is installable the moment it is published, add a retry or delay — the scanning window can stretch to 15 minutes or more at peak.

  • notable Terraform

    Three flaws in the Terraform MCP server include cross-tenant credential reuse — hashicorp.com

    Security bulletin HCSEC-2026-23, published 28 July 2026, discloses three vulnerabilities in the HashiCorp Terraform MCP server, all in the streamable HTTP transport: CVE-2026-14869, server-side request forgery; CVE-2026-16496, an authorisation bypass in stateful mode; and CVE-2026-16498, cross-tenant credential reuse in stateless mode. Versions 0.2.1 through 1.0.0 are affected and 1.1.0 is the fix. A separate bulletin earlier in the month, HCSEC-2026-17, covers an arbitrary file read in Terraform Enterprise.

    Upgrade to 1.1.0 before exposing the MCP server to anything multi-tenant, and treat cross-tenant credential reuse as a disclosure event rather than a patch if you have been running stateless mode. The newest and least-audited layer of the toolchain is currently the one handing credentials to agents.

Languages, runtimes and frameworks

Sections
  • notable Node.js

    Node.js patches eleven vulnerabilities, three high, across all release lines — nodejs.org

    Security releases on 29 July 2026 (26.5.1, 24.18.1 and 22.23.2) fix eleven CVEs, led by three high-severity issues: an HTTP/2 header-retention flaw that bypasses maxSessionMemory, a re-entrant HTTP/2 send use-after-free affecting every release line, and a Permission Model bug that over-grants filesystem access. The batch also closes a header-truncation request-smuggling issue and updates the bundled undici and llhttp.

    Patch Node origins and server-side rendering workloads promptly. The HTTP/2 issues are reachable from ordinary traffic, and the low-rated request-smuggling fix matters most where Node forwards requests as a proxy.

  • notable PHP

    PHP patches SQL injection in the PostgreSQL driver — php.net

    PHP shipped two security releases in July 2026. On 2 July, 8.2.32, 8.3.32, 8.4.23 and 8.5.8 fixed CVE-2026-14355, a memory-corruption flaw in openssl_encrypt with AES-WRAP-PAD. On 30 July, 8.2.33, 8.3.33, 8.4.24 and 8.5.9 fixed CVE-2026-17543, a SQL injection in the PGSQL extension through an E'...' backslash breakout, alongside CVE-2026-17544.

    Take the 30 July release. A SQL injection reachable through the driver's own string handling is not something an application-level prepared statement necessarily protects against, so patch rather than reasoning about whether your query builder is safe.

  • notable Symfony

    Symfony 8.0 reaches end of support after eight months — symfony.com

    Symfony 8.0 reached end of support for both bug fixes and security in July 2026, eight months after its November 2025 release alongside 7.4 LTS. Symfony 8.1, released in May 2026, is the current standard line.

    Anyone who adopted 8.0 at release needs to be on 8.1 already.

Static site and web tooling

Sections
  • critical Nuxt

    Nuxt patches a critical developer-host RCE and cross-user payload disclosure — nuxt.com

    Nuxt published a security batch on 27 July 2026 across 4.5.1, 3.21.10 and DevTools 3.3.1. GHSA-279x-mwfv-vcqv is Critical: an unauthenticated DevTools remote procedure call allows arbitrary command execution on the developer's host. GHSA-wm8w-6qjm-cv43 is High and discloses user payload data through a cached _payload.json on cached pages, affecting 4.x from 4.4.0. Further High-severity issues cover server-side code execution via server island props, a route-rule authorisation bypass through mixed-case paths, a regression introduced by the fix for CVE-2026-53721, and denial of service on /__nuxt_island.

    Run npx nuxt upgrade --dedupe. The cached-payload issue is the platform-level one: if pages were cached while a vulnerable version was live, one user's payload may have been served to another, which is a disclosure to assess rather than a bug to patch.

  • notable Next.js

    Next.js moves to monthly scheduled security releases — nextjs.org

    Next.js announced a formal security release process on 13 July — scheduled patch releases with advance notice roughly once a month, with ad hoc patches kept for urgent or actively exploited issues. The first scheduled security release followed a week later, fixing four high and five medium severity vulnerabilities in 16.2.11 (active LTS) and 15.5.21 (maintenance LTS).

    Upgrade to 16.2.11 or 15.5.21, and fold the monthly Next.js security window into your patching cadence alongside the CMS release windows you already track.

  • notable React Router

    React Router 8 ends life for version 6 and Remix 2 — remix.run

    Released 17 June 2026, React Router v8 requires Node 22.22.0 or later, Vite 7 or later and React 19.2.7 or later. The react-router-dom package is removed, the CommonJS build is dropped in favour of ESM only, and the deprecated data parameter on meta APIs becomes loaderData. React Router v6 and Remix v2 are declared end of life with no further security patches; v7 continues to receive them.

    Two silent breakers here: the Node floor and the loss of the CommonJS build. Check both before upgrading. If you are still on v6 or Remix v2, they now receive no further security patches — and react-router-dom 6.30.2 to 6.30.4 carry a July open-redirect advisory with no patched version.

    Update, August 2026: React Router 6.30.5 and 6.30.6, released 18 August, fix double-slash normalisation in useNavigate. GitLab's advisory database lists 6.30.6 as the fix for the July open-redirect advisory, but GitHub's advisory still lists no patched react-router-dom version.

Build on what the radar tracks

Integrations

How the CMSs, static site generators, and CI/CD tooling the radar tracks work with Quant.

Learn more

AI applications

Build RAG applications, chatbots, semantic search, and AI-powered features on Australian infrastructure.

Learn more

For developers

REST APIs, GitHub Actions, and SDKs — deploy static sites or containers with full API access.

Learn more