May 2026

Claude Platform on AWS reaches general availability — aws.amazon.com

AWS announced general availability of Claude Platform on AWS on 11 May, making it the first cloud provider to offer the native Claude Platform experience through an existing AWS account. Claude Managed Agents, advisor strategy, a files API, Skills and an MCP connector are in beta; web search, web fetch, code execution, prompt caching, citations and batch processing are not marked beta. It launches in 17 regions including Sydney and Melbourne, billed through AWS with IAM credentials and CloudTrail logging. Claude Platform on AWS is operated by Anthropic and processes data outside the AWS security boundary, whereas Bedrock is AWS's own managed inference service. On 28 May AWS made Claude Opus 4.8 available through both Bedrock and Claude Platform on AWS.

If data sovereignty matters to you, check whether a workload needs Claude Platform's native feature set or is better served by Bedrock, and confirm regional availability before adopting either.

MCP publishes release candidate of its next specification — blog.modelcontextprotocol.io

On 21 May 2026 the Model Context Protocol project published the release candidate of the 2026-07-28 specification, opening a ten-week validation window before final publication. Headline changes: a stateless protocol core that removes the initialize handshake and session IDs so requests can route to any server instance, a formal extensions framework, authorisation hardening aligned to OAuth 2.0 and OIDC, and a feature lifecycle policy with minimum 12-month deprecation windows.

Teams running MCP servers should review the release candidate now — the stateless core changes how servers deploy behind load balancers and CDNs, and feedback lands before the spec freezes, not after.

WordPress AI plugin reaches 1.0.0 with request logging and connector governance — make.wordpress.org

The canonical WordPress AI plugin hit 1.0.0 on 19 May 2026. The release adds a Request Logging experiment for auditing AI requests and responses across core, plugins and themes, a Connector Approvals experiment giving administrators control over which plugins may use configured AI connectors, enhanced comment moderation with sentiment and toxicity filtering, and AI alt-text generation in the media editor.

Sites experimenting with WordPress AI features now have the observability and governance controls to justify enabling them beyond staging — start with request logging.

Unbound patches possible code execution in DNSSEC validation — nlnetlabs.nl

NLnet Labs published CVE-2026-33278 on 20 May 2026 and rated it Critical on its own advisory register — deep copying a data structure erroneously overwrites a destination pointer during DNSSEC validation, causing denial of service and possibly arbitrary code execution. Affected versions run from Unbound 1.19.1 up to and including 1.25.0. The same batch carries CVE-2026-42944, a heap overflow, and CVE-2026-42959, a crash during DNSSEC validation, both rated High, plus eight further CVEs fixed in the same Unbound 1.25.1 upgrade.

Patch on the emergency path if you run Unbound as a validating resolver, because the flaw sits in the validation path itself and is reachable by an attacker who controls a zone you validate. Note where the affected range starts: 1.19.1 is the KeyTrap fix release, so anyone who patched in February 2024 and then treated the resolver as done is inside the range. The High-rated companions need no separate change window.

Let's Encrypt begins issuing 45-day certificates — letsencrypt.org

By 14 May 2026 an opt-in tlsserver ACME profile was issuing 45-day certificates. Let's Encrypt's announced later steps are a 64-day classic profile on 10 February 2027 and a 45-day classic profile on 16 February 2028, within the CA/Browser Forum's phased reduction of maximum certificate lifetimes — 200 days this year, 100 days in 2027 and 47 days by 2029. Let's Encrypt also limited its tlsclient client-certificate profile to accounts that had already used it, ahead of ending it on 8 July. Manual certificate renewal is on borrowed time — a point underlined on 8 May, when Let's Encrypt temporarily halted issuance after finding its new cross-signed intermediates were missing the serverAuth EKU; it said it would not revoke subscriber certificates.

Inventory any certificates you renew by hand and automate them — 100-day maximum lifetimes arrive in 2027, and manual renewal won't keep up. Shorter lifetimes also shrink the margin for issuance outages, so confirm your ACME clients retry failures and honour ARI renewal windows.

nginx patches six CVEs, then a second rewrite-module flaw nine days later — nginx.org

nginx 1.30.1 and 1.31.0, released 13 May 2026, fix six vulnerabilities: a buffer overflow in the rewrite module (CVE-2026-42945), HTTP/2 request injection in the proxy module, HTTP/3 address spoofing, a use-after-free in OCSP resolver requests and two buffer overreads. A further rewrite-module buffer overflow (CVE-2026-9256) followed in 1.30.2 and 1.31.1 on 22 May, with njs 0.9.9 fixing a heap overflow in between.

nginx fronts a large share of origin stacks — patch to 1.30.2 or later in one step and pick up both May batches together.

ASD publishes Opportunities for AI in cyber defence — cyber.gov.au

Official guidance mapping AI use cases to the ISM's six functions (Govern, Identify, Protect, Detect, Respond and Recover), with a supply-chain section and a vendor-questions appendix that asks which jurisdictions process or store customer data. ASD first published it on 27 May 2026.

Appendix A is a ready-made due-diligence checklist — put its 22 questions across eight categories to every AI vendor in your supply chain, starting with data jurisdiction.

Related reading: What the ASD asked. What we built.

Privacy Act coverage of "tranche 2" AML entities takes effect on 1 July — oaic.gov.au

Under the AML/CTF reforms, real estate professionals, dealers in precious metals and stones, and professional service providers — lawyers, conveyancers, accountants — come under the Privacy Act from 1 July 2026, many of them small businesses new to the Act. The OAIC published updated guidance for these newly covered entities on 27 February 2026.

If you or your clients operate in these sectors, review the OAIC's guidance before 1 July. Privacy obligations will apply to personal information handled for AML/CTF purposes, for many of these businesses for the first time.

Australia establishes its Cyber Incident Review Board — minister.homeaffairs.gov.au

On 4 May 2026 the Minister for Cyber Security announced the establishment of the Cyber Incident Review Board under the Cyber Security Act 2024, delivering a commitment of the 2023-2030 Australian Cyber Security Strategy. Chaired by Telstra's global CISO Narelle Devine, with members drawn from UNSW, Allens, Boeing Australia, NBN Co, Toll Group and SA Power Networks, the board conducts independent no-fault reviews of significant cyber incidents and delivers recommendations to government and industry.

Government and critical-infrastructure organisations can now be drawn into statutory post-incident reviews — treat incident documentation, logging and timeline reconstruction as material that may feed a no-fault review, not just internal retrospectives.

Highly critical Drupal core security release — drupal.org

Drupal shipped a highly critical core security update — 20 out of 25 on Drupal's severity scale — on 20 May across all supported branches. SA-CORE-2026-004 (CVE-2026-9082) is an SQL injection in core's database API that anonymous users can exploit, and it affects only sites running PostgreSQL. The security team warned exploits could appear within hours or days of release, and on 22 May Drupal raised the score to 23 out of 25 after exploit attempts were detected in the wild. Manual patch files were offered for end-of-life Drupal 8.9 and 9 on a best-effort basis.

Patch immediately. Statically delivered sites reduce exposure since Drupal isn't public facing, but the editorial origin still needs the update.

WordPress 7.0 "Armstrong" released — wordpress.org

The 20 May release adds a provider-agnostic AI Client, a JavaScript counterpart to the Abilities API, a new Connectors screen for managing external connections and a refreshed admin with a Cmd+K command palette and smoother transitions. Real-time collaboration was cut late over stability concerns.

Test plugin compatibility on a staging copy before upgrading. The AI Client API is one to watch for headless and statically delivered setups.

Drupal core confirms its 2026 release timeline — thedroptimes.com

Drupal's core schedule listed 11.4.0-beta1 for the week of 18 May 2026 and the release candidate for the week of 1 June, with 11.4.0 itself due the week of 22 June.

Diary work only. Treat the schedule as a plan rather than a commitment. The window between a frozen API and the stable release is the last cheap moment to find a contributed-module blocker.

Malicious node-ipc versions published to npm — thehackernews.com

On 14 May three malicious versions of node-ipc (9.1.6, 9.2.3, 12.0.1) landed on npm from a compromised maintainer account, each carrying an obfuscated credential stealer. The 9.x builds run on any host that loads them; 12.0.1 is gated to a pre-computed module path.

Pin dependencies to exact versions and treat releases published in the last few days with suspicion — the window right after publish is when supply chain attacks do their damage.

Actions run on Node 24 by default from 16 June — github.blog

GitHub is forcing the Node 24 runtime for JavaScript actions. A 19 May 2026 editor's note on GitHub's changelog post moved the default to 16 June 2026. Actions still targeting Node 20 can break once that default lands.

Audit your workflows before 16 June. If you pin actions to SHAs (you should), make sure the pinned refs are Node 24 compatible while you're in there.

npm staged publishing arrives — github.blog

npm made staged publishing generally available on 22 May 2026. A version sent with npm stage publish waits in a stage queue until a human maintainer approves it with a 2FA challenge, and a trusted publishing configuration can be limited to stage-only. Existing tokens keep their direct-publish rights, so staging protects only the publishing paths switched over to it.

Enable it on every package your organisation publishes, starting with the ones a client build resolves at deploy time. Set trusted publishing to stage-only and retire tokens that can publish directly, because staging blunts a maintainer compromise only when no direct-publish path remains.

Twig flaw allows PHP code execution and a full sandbox escape — symfony.com

CVE-2026-46640, published 20 May 2026, lets attacker-controlled template content reach Twig's macro-reference compilation and be compiled straight into PHP source — arbitrary code execution that bypasses the sandbox entirely, even with an empty allowlist. Twig 3.15.0 through 3.25.x are affected; the fix is Twig 3.26.0. Twig 3.27.0 followed on 27 May with five more sandbox fixes, including CVE-2026-46636.

Twig underpins Drupal and Symfony applications: update to Twig 3.27.0 or later everywhere, and treat any feature that lets users or editors supply template source as an emergency patch case.

PHP security releases land across all four supported branches — php.net

On 7 May 2026 PHP shipped security releases 8.5.6, 8.4.21, 8.3.31 and 8.2.31. The 8.5.6 changelog lists twelve CVE IDs, including a cross-site scripting flaw in the PHP-FPM status endpoint (CVE-2026-6735), SQL injection via NUL bytes in PDO_Firebird quoting (CVE-2025-14179), two mbstring memory-safety bugs, three SOAP issues, and a segfault in file_get_contents over HTTPS through a proxy (CVE-2026-12184).

Patch PHP across Drupal, WordPress and Laravel origins — the FPM status-endpoint XSS is directly relevant to typical hosting setups that expose the status page internally.

A second Symfony mass security release in a week fixes a firewall bypass — symfony.com

Released 27 May 2026, Symfony 8.0.13, 7.4.13, 6.4.41 and 5.4.53 include CVE-2026-48489, a security firewall bypass driven by user-supplied input and rated High by GitHub as CNA (CVSS 8.7). It is the second mass release in a week, following a 20 May batch; between them the two batches carried 47 CVE advisories across Symfony and Twig. Much of that volume — 19 of the vulnerabilities — came from an AI-assisted audit Symfony disclosed on 21 May, though this particular bypass was reported independently. Twig shipped two sandbox-focused security releases in the same period, 3.26.0 and 3.27.0.

Patch to the 27 May versions, not the 20 May ones. A firewall bypass means authorisation rules did not run, so review access logs for the exposure window rather than treating the upgrade as the end of it.

Next.js patches a High middleware bypass via segment-prefetch routes — github.com

On 6 May 2026 Next.js published GHSA-267c-6grr-h53f, a High middleware and proxy bypass via segment-prefetch and .rsc routes, fixed in 15.5.16 and 16.2.5. That fix did not cover middleware.ts under Turbopack, so a follow-up advisory, GHSA-26hh-7cqf-hhc6, was fixed in 15.5.18 and 16.2.6 on 7 May. The 6 May releases also patched middleware and proxy bypasses via dynamic route parameter injection and in Pages Router applications using i18n. Middleware commonly gates authentication in App Router applications, so a prefetch-route bypass is an authentication-control failure, not a renderer-only bug.

Upgrade self-hosted Next.js applications to 15.5.18 or 16.2.6 or later immediately, and treat middleware as defence-in-depth rather than the sole authentication layer.

Hugo 0.162 stops rendering HTML content files by default — github.com

Released 26 May 2026, Hugo 0.162.0 denies text/html content files by default behind a new security.allowContent allowlist, because Hugo emits the content of such files verbatim. Markdown files are not affected. The change fixes CVE-2026-50133, a Moderate cross-site scripting flaw via HTML content files. The same release rejects symlinked entries in resources.Get, fixing CVE-2026-50135, a symlink confinement bypass affecting versions 0.123.0 to 0.161.1.

Check whether any site you build has .html files under /content before upgrading — Hugo fails a build that uses anything outside its security allowlist, so convert those pages or allow text/html in security.allowContent.

Astro ships 6.3 and 6.4, Starlight 0.39 — astro.build

A busy month upstream: 6.3 added experimental advanced routing, 6.4 introduced a pluggable Markdown pipeline with a Rust-based processor, and Starlight 0.39 brought flexible autogenerated sidebars. The Astro 7 alpha continues with Vite 8 support.

If your build relies on Markdown rendering quirks, test output carefully before adopting 6.4 — the processor swap can change generated HTML.