Radar · 2026-03
March 2026
The axios npm package is hijacked to deliver cross-platform malware, the TeamPCP campaign compromises Trivy, KICS, LiteLLM and Telnyx, Cyera discloses a new LangChain path traversal flaw, a critical access bypass hits the Unpublished Node Permissions module and the maximum TLS certificate lifetime drops to 200 days.
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 OWASP
OWASP publishes a data security framework for generative AI — genai.owasp.org
On 17 March 2026 the OWASP GenAI Security Project published "GenAI Data Security Risks & Mitigations 2026," an open framework for the data layer of enterprise AI adoption. It maps novel attack surfaces across the data lifecycle — training data, fine-tuning, prompts and model outputs — with AI-specific security testing and monitoring guidance.
Use it as the reference for what data can safely flow into prompts, RAG stores and fine-tuning when wiring AI into CMS and hosting workflows — the questions your security review should be asking now have a vendor-neutral source.
- notable LangChain
Cyera discloses a new LangChain path traversal flaw and revisits two older ones — thehackernews.com
Cyera's late-March 2026 research covered three LangChain and LangGraph flaws, only one of them new: a path traversal in the prompt-loading API (CVE-2026-34070, CVSS 7.5). The other two were already public and patched: SQL injection in LangGraph's SQLite checkpoint implementation via metadata filter keys (CVE-2025-67644, CVSS 7.3), published in December 2025 and fixed in langgraph-checkpoint-sqlite 3.0.1, and an unsafe-deserialisation flaw that leaks API keys and environment secrets (CVE-2025-68664, CVSS 9.3), first disclosed by Cyata in December 2025 as LangGrinch. In the week before disclosure LangChain drew more than 52 million downloads, LangChain-Core more than 23 million and LangGraph more than 9 million. The AI framework layer is now squarely part of the supply chain, and it is younger and less hardened than the web frameworks around it.
Pin and patch AI framework dependencies on the same cadence as the rest of the stack, and check whether anything in your agents deserialises state or checkpoints from a location a user can influence.
- fyi MCP
Model Context Protocol publishes its 2026 roadmap — modelcontextprotocol.io
The Model Context Protocol project published its 2026 roadmap on 9 March, shifting from date-based releases to four priority areas: transport scalability, agent communication, governance and enterprise readiness. Working groups drive deliverables in the first three; a dedicated enterprise working group does not yet exist. A move towards a stateless protocol core is flagged, which will matter for anyone running MCP servers behind standard HTTP infrastructure.
Nothing to change yet, but the stateless core is the flag to follow. It decides whether an MCP server can sit behind an ordinary load balancer or needs sticky sessions, which is an infrastructure question rather than a protocol one — so anyone running servers should read the transport scalability group's output rather than waiting for a version number.
Security and edge
Sections- critical TLS
Maximum TLS certificate lifetime drops to 200 days — cabforum.org
The first milestone of the CA/Browser Forum schedule took effect on 15 March 2026: publicly trusted TLS certificates issued from that date are capped at 200 days, down from 398. Lifetimes reduce again to 100 days from 15 March 2027 and 47 days from 15 March 2029, so annual manual renewal processes no longer work.
Inventory any certificates renewed manually and move them to automated issuance such as ACME before the shorter caps arrive.
- notable nginx
nginx patches six CVEs across mainline and stable — nginx.org
nginx 1.29.7 and 1.28.3, released 24 March 2026, fix six vulnerabilities: buffer overflows in the WebDAV and MP4 modules, a NULL dereference and an injection issue in the mail proxy, and an OCSP result bypass in the stream module. Some of the flaws date back to 0.5.x-era code; the project rates them all medium or low.
Patch origins that serve MP4 assets, expose WebDAV or terminate stream-level TLS with OCSP — and treat third-party "critical RCE" framing of this batch with suspicion, since nginx's own ratings top out at medium.
- fyi TLS
Certbot brings six-day and IP-address certificates to the masses — letsencrypt.org
On 11 March 2026 Let's Encrypt announced Certbot support for its six-day certificate profile and for IP-address certificates, via
--preferred-profileand--ip-address. The IP-address flag landed in Certbot 5.3; Let's Encrypt recommends 5.4 or later for webroot IP issuance. IP certificates require the six-day profile, and Certbot can obtain but not yet auto-install them into web servers.If your automation is Certbot-based, verify it handles six-day renewal cadences before adopting the short-lived profile — and note IP certificates now open TLS for endpoints without hostnames.
Standards and compliance
Sections- critical Cyber Security Act
Australia's mandatory smart-device security standard takes effect — homeaffairs.gov.au
The Cyber Security (Security Standards for Smart Devices) Rules 2025, made under the Cyber Security Act 2024, commenced on 4 March 2026 after a twelve-month transition. Most smart devices manufactured on and from 4 March 2026 for personal, domestic or household use must meet the standards: no universal default passwords, a published vulnerability-reporting channel, and a disclosed security-update support period. Desktops, laptops, smartphones and tablets are excluded. Products manufactured earlier are not required to comply.
Procurement teams can now demand conformance statements for in-scope connected devices manufactured on or after 4 March 2026.
- notable ISM
ASD releases March 2026 Information security manual update — github.com
The March ISM update adds a cyber security principle making boards and executive committees accountable for secure, human-supervised and ethical use of artificial intelligence, introduces a Protect principle covering cyber supply chains, splits third-party software testing into initial and periodic testing controls, and stops staff who use their own phones or computers for OFFICIAL: Sensitive or PROTECTED work from granting access to unapproved AI agents.
Agencies and suppliers assessed against the ISM should review the changes document and map the new AI accountability and supply chain principles to their existing governance.
- fyi Privacy Act
OAIC releases exposure draft of the Children's Online Privacy Code — oaic.gov.au
On 31 March the OAIC released the exposure draft of the Privacy (Children's Online Privacy) Code for public consultation, with submissions open until 5 June. The code would apply to online services likely to be accessed by children, including websites, apps and educational tools, with requirements around best interests, targeted advertising consent and deletion requests.
Organisations running services accessed by children should review the draft and consider making a submission before 5 June; the code must be registered by 10 December 2026.
CMS and platforms
Sections- notable Drupal
Critical access bypass in Unpublished Node Permissions module — drupal.org
The Drupal security team published SA-CONTRIB-2026-029 on 11 March for the Unpublished Node Permissions module, a critical access bypass where access to unpublished translated nodes is not consistently controlled. A moderately critical information disclosure in the AI module (SA-CONTRIB-2026-028) was fixed the same day.
If you use Unpublished Node Permissions, update to 8.x-1.7 now. Sites running the AI module should update to 1.1.11 or 1.2.12.
- notable WordPress
WordPress ships 6.9.2 security release, then patches it twice in 48 hours — wordpress.org
WordPress 6.9.2, released 10 March 2026, fixes ten vulnerabilities including stored XSS in navigation menus, blind SSRF, a PoP-chain weakness in the HTML API and Block Registry, PclZip path traversal and an XXE in the bundled getID3 library. But not all fixes were fully applied: 6.9.3 followed the same day for a template-loading regression that blanked front ends on themes passing stringable objects as file paths, and 6.9.4 shipped on 11 March to re-apply three security fixes that 6.9.2 and 6.9.3 carried incompletely.
Confirm sites landed on 6.9.4 specifically — anything that auto-updated to 6.9.2 or 6.9.3 and stopped still carries three incompletely patched issues.
- fyi WordPress
WordPress 7.0 release candidate delayed, then the 7.0 cycle extended — make.wordpress.org
The WordPress core team announced on 19 March that WordPress 7.0 Release Candidate 1 would be delayed to 24 March while the team worked through Real-Time Collaboration performance, client-side media image optimization and release package size. RC1 shipped on 24 March, but on 31 March the core team extended the 7.0 cycle by a few weeks to settle key architectural details, so the planned 9 April final release no longer held.
Keep testing against the 7.0 betas and the delayed RC.
Update, May 2026: WordPress 7.0 was released on 20 May 2026 without real-time collaboration, which the core team removed from 7.0 on 8 May.
Supply chain, CI/CD and IaC
Sections- critical Supply chain
TeamPCP campaign compromises Trivy, KICS, LiteLLM and Telnyx — thehackernews.com
Between 19 and 27 March, the TeamPCP group compromised the distribution channels of four widely used developer tools: the Trivy scanner (binaries, GitHub Actions and Docker images), Checkmarx KICS, and the LiteLLM and Telnyx packages on PyPI. The injected malware harvested cloud credentials, SSH keys and CI/CD secrets from developer and pipeline environments.
Audit pipelines for affected versions of these tools, rotate any credentials that ran through affected CI jobs, and pin security tooling to verified versions rather than tracking latest.
- critical npm
axios npm package hijacked to deliver cross-platform malware — thehackernews.com
On 31 March, attackers took over a maintainer account for axios, one of the most widely used JavaScript HTTP clients (more than 83 million weekly downloads at the time of reporting), and published malicious versions 1.14.1 and 0.30.4. The versions pulled in a rogue dependency whose install script deployed a remote access trojan on macOS, Windows and Linux. Researchers found significant overlap between the macOS payload and WAVESHAPER, a backdoor linked to a North Korean threat actor, but who was behind the compromise had not been established at the time of writing.
Check lockfiles and build logs for installs of the affected versions during the exposure window. If found, treat the host as compromised and rotate all credentials. Dependency pinning and install-script controls limit exposure to this class of attack.
- fyi GitHub Actions
GitHub publishes its 2026 security roadmap for Actions — github.blog
In March GitHub published its GitHub Actions 2026 security roadmap, a direct response to CI/CD-targeted attacks. Planned features include workflow lockfiles that pin action dependencies to commit SHAs, policy controls over who and what can trigger workflows, a native egress firewall and scoped secrets.
Worth reading if you maintain build pipelines; the roadmap signals defaults that will change over the year, and pinning actions to commit SHAs is good practice you can adopt today.
Languages, runtimes and frameworks
Sections- notable Node.js
Node.js security releases across all supported lines — nodejs.org
Node.js shipped security releases on 24 March covering two high, five medium and two low severity issues, including a TLS flaw where a synchronously thrown SNICallback exception bypasses error handling and crashes the process. Updated versions are 20.20.2, 22.22.2, 24.14.1 and 25.8.2, along with undici dependency updates.
Update build and server environments to the patched release for your line. Node.js 20 reaches end of life on 30 April 2026, so plan a move to 22 or 24.
- notable Laravel
Laravel 11 security support ends; Laravel 13 ships five days later — laravel.com
Laravel 11 stopped receiving security fixes on 12 March 2026 under the framework's two-year support policy, so any new vulnerability in it remains unpatched upstream. Laravel 13 was released on 17 March with a PHP 8.3 minimum, minimal breaking changes, and security fixes running until 17 March 2028.
Move applications still on Laravel 11 to 12 or 13 now; the project designed the upgrade to 13 to require little application code change.
- notable Python
Python hardens email header generation — python.org
Released 3 March 2026, Python 3.12.13, 3.11.15 and 3.10.20 carry CVE-2024-6923, where
email.generator.BytesGeneratornow refuses to serialise headers that are unsafely folded or delimited.Patch, then test any code that constructs email headers from user input — the new behaviour raises rather than silently emitting, so a latent injection becomes a visible exception on upgrade.
Static site and web tooling
Sections- notable Vite
Vite 8 makes Rolldown the bundler for every build — vite.dev
Released 12 March 2026, Vite 8 ships Rolldown as a single unified bundler in place of esbuild and Rollup, with a compatibility layer that auto-converts esbuild settings and
rollupOptions. Node 20.19 or later, or 22.12 or later, is required. For larger or more complex projects the project recommends a two-step migration viarolldown-viteon Vite 7; for most projects it expects the direct upgrade to be smooth.Expect chunk names, hashes and plugin behaviour to move. Compare built output before and after on a real site rather than trusting the compatibility layer, and plan for a full cache invalidation on the release that ships it.
- fyi Astro
Astro 6.0 and 6.1 ship Fonts API, stable CSP and image encoding defaults — astro.build
Astro 6.0, released 10 March, ships a built-in Fonts API, stable Content Security Policy support, live content collections that fetch content at request time, and an experimental Rust-based compiler. Astro 6.1, released 26 March, follows up with global image encoding controls that let you set codec-specific defaults for JPEG, WebP, AVIF and PNG once in config rather than per image, plus Markdown configuration options and updated i18n hooks.
If you set per-image quality options in templates, consolidating them into the new global image encoding config can simplify builds and standardise output.
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