Radar · 2026-06
June 2026
Red Hat npm packages are compromised with a credential-stealing worm, OpenSSL patches 18 vulnerabilities across five public release lines, a Drupal core security window patches critical JSON:API object injection, ASD consults on evolving the Essential Eight and Astro 7.0 ships with a Rust compiler and faster builds.
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 Bedrock
Claude Fable 5 reaches Bedrock, then access is revoked within days — aws.amazon.com
AWS announced general availability of Claude Fable 5 — the first generally available Mythos-class model — on Amazon Bedrock and the Claude Platform on AWS on 9 June 2026, in the US East (N. Virginia) and Europe (Stockholm) Regions. Accounts had to opt into data sharing, and Anthropic required 30-day retention of inputs and outputs plus human review. The 15 June AWS Weekly Roundup records that on 12 June Anthropic asked AWS to revoke all customer access to Claude Fable 5 and the preview-only Claude Mythos 5 to comply with a US Government export-control directive. Other Claude models, including Opus 4.8, were unaffected.
Teams that onboarded the model that week had workloads break mid-month — keep model choice configurable and a tested fallback in the same region, since catalogue models can now disappear for regulatory as well as deprecation reasons.
Update, July 2026: On 1 July 2026 Amazon said Claude Fable 5 was available again on Amazon Bedrock.
Update, September 2026: On 1 September 2026 AWS made Claude Fable 5.1 generally available on Amazon Bedrock and the Claude Platform on AWS, as a Covered Model with extra data retention, safety review and access policies.
- fyi MCP
MCP adds enterprise-managed authorisation through your identity provider — blog.modelcontextprotocol.io
On 18 June 2026 the MCP project published Enterprise-Managed Authorization, a stable extension that moves MCP server authorisation from per-user OAuth prompts to central identity-provider control, with users connected automatically on first login by group or role. Okta ships support first via Cross App Access; participating clients include Claude, Claude Code and VS Code, with servers from Asana, Atlassian, Canva, Figma, Granola, Linear and Supabase on board. The project encourages more clients, servers and identity providers to add support, and an EMA Interest Group is open for discussing and iterating on the extension.
Organisations running MCP servers against internal tooling can now gate access centrally instead of relying on ad-hoc user OAuth grants — worth evaluating before wider agent rollouts.
- fyi WordPress
WordPress AI team previews AI Client streaming and embeddings for 7.1 — make.wordpress.org
On 19 June 2026 the WordPress AI team set out what's coming to the AI Client in WordPress 7.1: generation streaming in the PHP AI Client, the framework underneath it, because streaming needs requests that run for minutes while most servers time out after 30 seconds and WordPress's request system does not support long requests by default, plus embeddings support for semantic search, alongside backward-compatible fixes. The work stays foundational, building ecosystem plumbing rather than shipping generative features directly into core.
Nothing to adopt from a preview, but both features are worth knowing before a client asks. Streaming only works where the server allows requests of up to several minutes, which ordinary shared hosting usually does not, and embeddings support is what makes semantic search possible without a separate service. Together they decide whether WordPress AI features can run inside an ordinary hosting envelope.
Security and edge
Sections- notable Apache
Apache HTTP Server 2.4.68 fixes 13 vulnerabilities — httpd.apache.org
The 8 June release addresses 13 security issues across core and modules, including use-after-free and heap buffer overflow flaws plus cross-site scripting and denial of service vectors, affecting versions back to 2.4.0. Apache still fronts a large share of CMS origin servers, and web server flaws are routinely scanned for within days of disclosure.
Update origin servers to 2.4.68, or confirm your distribution has backported the fixes into its packaged version.
- notable OpenSSL
OpenSSL patches 18 vulnerabilities across five public release lines — openssl-library.org
OpenSSL's 9 June 2026 advisory covers eighteen CVEs — one High, five Moderate and twelve Low — fixed in 4.0.1, 3.6.3, 3.5.7, 3.4.6 and 3.0.21, with 1.1.1zh and 1.0.2zq issued to premium-support customers on the same day, so seven branches were patched in total. The headline is CVE-2026-45447, a high severity heap use-after-free in PKCS7_verify affecting every release line since 1.0.2; moderate issues include forged CMS AuthEnvelopedData messages, a double-free in OCSP stapled-response checking and two QUIC denial-of-service bugs.
OpenSSL underpins TLS termination on most edge and origin stacks — confirm your distros and base images pick up the June patch set, especially anywhere OCSP stapling or QUIC is enabled.
- fyi TLS
Let's Encrypt CRLs briefly omitted revoked certificates — community.letsencrypt.org
On 3 June 2026 Let's Encrypt disclosed that a database replication issue caused recently revoked certificates to be temporarily missing from its published CRLs, so some revoked but unexpired certificates could appear valid to CRL-based checkers. Subsequent CRL updates re-included the affected entries. Let's Encrypt filed a preliminary incident report as Mozilla bug 2044788.
The lists corrected themselves. Let's Encrypt did not tell subscribers to take a step. The lesson is worth keeping: a revocation list that fetches and parses cleanly can still be incomplete, so treating an absent CRL entry as proof of validity trusts a freshness the checker cannot verify.
Standards and compliance
Sections- critical Privacy Act
OAIC finds privacy breaches in tracking pixel investigation — oaic.gov.au
On 11 June, announced 24 June, the Privacy Commissioner determined that Medmate Australia and Monash IVF interfered with individuals' privacy by collecting sensitive information through third-party tracking pixels on their websites. The OAIC said website providers must obtain consent where tracking pixels collect sensitive information. Existing OAIC pixels guidance already treats people as reasonably identifiable where pixel data (such as an IP address, URL or hashed email) can be linked or matched with what the platform holds, even if they are not named in the pixel payload.
Audit the third-party pixels, tags and analytics scripts on your sites, especially on pages handling health or other sensitive information, and confirm collection is disclosed and justified under the APPs.
- notable ISM
ASD releases June 2026 Information security manual update — cyber.gov.au
The June ISM update adds 20 controls, including a requirement to use cyber threat intelligence services to support event detection (ISM-2116), new guidance on AI applications and AI-assisted software development, and controls advising personnel against posting clearance and duty details online. Terminology moved to 'ASD-approved cryptography'.
Agencies and suppliers assessed against the ISM should review the changes document and factor the threat intelligence and AI development controls into their next assessment cycle.
- fyi Essential Eight
ASD consults on evolving the Essential Eight into an Essentials series — cyber.gov.au
On 15 June 2026 ASD announced a consultation on evolving the Essential Eight into a broader Essentials series, with the current guidance becoming its first chapter, "Essentials for enterprise IT" — prioritised, threat-informed mitigations. Consultation runs via the ASD Cyber Security Partnership Program portal until 12 July 2026.
Essential Eight maturity levels are embedded in agency postures, IRAP assessments and vendor questionnaires — track the transition, and avoid over-investing in Essential-Eight-specific tooling narratives while the successor takes shape.
Update, October 2026: On 15 October 2026 ASD launched the Essentials, with Essentials for enterprise IT as the evolution of the Essential Eight, and published guidance on transitioning an existing Essential Eight implementation, including how to reuse assessment evidence.
CMS and platforms
Sections- notable Drupal
Drupal core security window patches critical JSON:API object injection — drupal.org
On 17 June 2026 the Drupal security team published five core advisories, led by SA-CORE-2026-005, a critical PHP object injection flaw reachable via JSON:API that closes a gap left by 2019's fix. The batch also includes SA-CORE-2026-008, an SSRF in Media's oEmbed URL discovery that requires
$settings['media_oembed_discovery_trusted_host_patterns']in settings.php if you use URL discovery, plus gadget-chain, cache-poisoning and validation fixes. Updated releases are 10.5.12, 10.6.11, 11.2.14 and 11.3.12. A contrib wave followed on 24 June, including a critical SQL injection in Geolocation Field and access-bypass fixes in Paragraphs and the AI module family.Update core in this window and, if you use oEmbed URL discovery, set
media_oembed_discovery_trusted_host_patternsin settings.php to the hosts you trust, then take the 24 June contrib advisories — especially if you run Paragraphs, Geolocation Field or the Drupal AI modules. - fyi Drupal
Drupal 11.4.0 misses its late-June release window — thedroptimes.com
Drupal 11.4.0, scheduled for the week of 22 June, was delayed while core waited on security-release work and dependency security patches.
No action needed on the delay itself. Plan a testing window for the 11.4 update and start working through deprecation notices in custom modules.
Update, July 2026: Drupal 11.4.0 was released on 1 July 2026.
Supply chain, CI/CD and IaC
Sections- critical npm
Red Hat npm packages compromised with credential-stealing worm — bleepingcomputer.com
More than 30 packages in the @redhat-cloud-services npm namespace, around 117,000 weekly downloads, were backdoored with a Shai-Hulud variant dubbed Miasma after a Red Hat GitHub account was compromised in late May via a malicious VS Code extension. The payload ran on npm install and harvested GitHub Actions secrets plus AWS, GCP, Azure, Kubernetes and npm tokens. Red Hat closed the incident on 17 June.
Check lockfiles for affected package versions, rotate any CI/CD and cloud credentials on machines that installed them, and disable or gate npm install scripts in build pipelines.
- notable GitHub Actions
GitHub Actions runners now default to Node 24 — github.blog
From 16 June, GitHub Actions runners execute JavaScript actions on Node 24 by default, following Node 20's end of life in April. Older actions pinned to node20 keep working for now via an opt-out environment variable, but Node 20 will be removed from the runner entirely later in 2026, and macOS 13.4 and ARM32 self-hosted runners are not supported on Node 24.
Update workflows to current major versions of the actions you use, and update any actions you maintain to declare node24. Treat the opt-out variable as a short-term bridge only.
Update, September 2026: GitHub removed Node 20 from Actions runners on 23 September 2026, and the opt-out variable no longer works, so actions must run on Node 24.
- notable GitHub Actions
GitHub hardens Actions and npm against supply chain attacks — github.blog
A cluster of June changes closes common attack paths: actions/checkout v7 no longer checks out untrusted fork code on pull_request_target triggers by default (18 June, with the enforcement due to be backported to all supported major versions on 16 July), new actor and event policies control who and what can trigger workflows (18 June), high-impact npm accounts are locked read-only for 72 hours after an email change or 2FA recovery-code use (25 June), and untrusted workflow runs get a read-only Actions cache (26 June). GitHub also announced on 9 June that npm v12, estimated for July 2026, would disable package install scripts by default, with an approval mechanism for packages that legitimately need them.
Review workflows that use pull_request_target for reliance on the old checkout behaviour, and note that the planned backport means floating tags such as @v4 change too, not only v7. Set workflow trigger policies at the organisation level. Install scripts are the urgent one: npm 12 is due in July with them off by default, so audit which dependencies rely on them and put the approvals in place rather than waiting for a build to break.
Update, July 2026: npm 12 became generally available on 8 July 2026 with allowScripts off by default. GitHub moved the actions/checkout backport to 20 July 2026 and excluded v1; workflows on floating major tags such as @v4 pick up the change, while SHA, minor or patch pins need a manual upgrade.
Languages, runtimes and frameworks
Sections- notable Node.js
Node.js patches two high severity flaws across all supported lines — nodejs.org
The 18 June Node.js security releases (22.23.0, 24.17.0 and 26.3.1) fix twelve CVEs, including a high severity WebCrypto flaw that lets crafted input crash the process (CVE-2026-48933) and a high severity TLS hostname normalisation mismatch enabling wildcard authentication bypass (CVE-2026-48618), plus updates to llhttp, nghttp2, OpenSSL and undici.
Update build and runtime environments to the patched release for your supported line (22, 24 or 26). Node.js says end-of-life versions are always affected by a security release, so move anything still on an end-of-life line.
- notable Laravel
Laravel patches CRLF injection in its default email validation rule — github.com
A 1 June advisory (CVE-2026-48019, rated high at 8.9) covers a CRLF injection flaw in Laravel's email validation that, combined with how Symfony Mailer handles certain character sequences, can let an unauthenticated attacker interfere with outbound mail — altering content, adding recipients or abusing the application's mail server as a relay. Any application that emails user-supplied addresses is in scope, which includes most authentication and contact-form flows.
Upgrade to Laravel 12.60.0 or 13.10.0. If you cannot upgrade immediately, sanitise user-supplied email addresses before they reach the mailer.
- notable Go
Go patches certificate handling and MIME parsing — go.dev
Released 2 June 2026, go1.26.4 and go1.25.11 carry security fixes in
crypto/x509,mimeandnet/textproto. Themimefix stops crafted headers with many invalid encoded-words from consuming excessive CPU inWordDecoder.DecodeHeader(CVE-2026-42504). Thenet/textprotofix stops attacker-controlled input appearing unescaped in error messages, where it could inject misleading content or terminal control bytes into output or logs (CVE-2026-42507).Rebuild Go services that decode MIME headers or parse headers from untrusted peers. Nothing here is urgent in isolation, but the parsing surface is the one that tends to sit directly on user input.
Static site and web tooling
Sections- notable Astro
Astro 7.0 released with Rust compiler and faster builds — astro.build
Astro 7.0 shipped on 22 June with the .astro compiler and Markdown pipeline rewritten in Rust and the bundler moved to Vite 8 with Rolldown, producing overall build times 15 to 61 per cent faster across six large documentation and project sites benchmarked by the Astro team. Route caching is now stable, and this is a major release with breaking changes. Starlight 0.41 adds Astro 7 support but drops Astro 6.
Review the migration guide before upgrading, and confirm your integrations and adapters support Vite 8. Astro 6 remains fine to run while you plan.
- notable Hugo
Hugo build-time request forgery reaches cloud metadata endpoints — github.com
GHSA-r46f-3rpw-hxrv, published 18 June 2026 and fixed in Hugo 0.163.1, is rated Moderate by the project and High (7.7, CVSS v4) by the GitHub Advisory Database. Alternate IPv4 encodings such as
http://2130706433/orhttp://0x7f000001/bypasssecurity.http.urlsdeny rules viaresources.GetRemote, reaching loopback, internal services and cloud metadata from the build. It affects 0.162.0 through 0.163.0. The same 0.163.1 release also patched a symlink confinement bypass inos.ReadFile(GHSA-c3wq-j5vh-68rc), which needs a planted symlink in a locally vendored theme.Upgrade to 0.163.1 or later. If you build untrusted or client-supplied Hugo sites on shared infrastructure, this is the threat model exactly — a build that can reach the metadata endpoint can retrieve instance credentials, so check whether that egress was ever reachable.
- fyi Browsers
June browser releases: field-sizing reaches Baseline, Safari 27 in beta — web.dev
Chrome 149, Chrome 150 and Firefox 152 shipped during June. Firefox's field-sizing support makes automatic form control sizing Baseline newly available across all major engines, Chrome 149 brings the rect() and xywh() shape functions to Baseline, and Chrome 150 adds text-fit font scaling, promise-returning scroll methods and the focusgroup attribute for declarative keyboard navigation. Safari 27 entered beta with transform-aware anchor positioning and a :heading pseudo-class.
field-sizing: content is now safe to adopt for self-sizing textareas and inputs — one less JavaScript workaround to maintain.
Build on what the radar tracks
Integrations
How the CMSs, static site generators, and CI/CD tooling the radar tracks work with Quant.
Learn moreAI applications
Build RAG applications, chatbots, semantic search, and AI-powered features on Australian infrastructure.
Learn moreFor developers
REST APIs, GitHub Actions, and SDKs — deploy static sites or containers with full API access.
Learn more