Selected events and fix thresholds
This retrospective covers 2026-03-01 to 2026-03-31. Sources were checked on 6 November 2026. The table lists historical fix thresholds in the corresponding branches. Before deploying, choose a currently supported release or a distributor package with the relevant backport; an old fix threshold is not a recommendation to install an obsolete branch.
For the selected items, this review confirms the disclosure or security release and its stated conditions. Active exploitation and historical CISA KEV or EPSS status are not asserted here. Missing exploitation evidence remains unknown.
| Event date | Product and advisory | Fix thresholds by branch |
|---|---|---|
| 2026-03-10 | WordPress | 6.9.2 |
| 2026-03-24 | Node.js | CVE-2026-21710 | 20.20.2 / 22.22.2 / 24.14.1 / 25.8.2 |
| 2026-03-11 | curl | CVE-2026-3783 | 8.19.0 / 8.16.1 / 8.14.2 |
WordPress: the March core security release
WordPress 6.9.2 includes fixes for several separate issues, including blind SSRF, stored XSS, authorization weaknesses and archive path traversal. The release also coordinates an external getID3 fix. Each feature has its own conditions; the notice does not establish one universal exploit against every installation.
Apply a current supported core release or verify the corresponding branch backport. Check media handling, editorial permissions and the enquiry route on a copy before updating the live site.
Node.js: request headers and availability (CVE-2026-21710)
A request containing the header name __proto__ can crash a Node.js HTTP server when application code reads req.headersDistinct. The exception occurs in a property getter. The March security release fixes the issue in the then-active 20, 22, 24 and 25 branches.
Check application and middleware use of req.headersDistinct. Update the deployed runtime, then verify API error handling and monitoring on controlled requests without testing a crash against production.
curl: redirects, netrc and bearer tokens (CVE-2026-3783)
A bearer token can reach another hostname after a redirect when the destination matches credentials in a netrc file, including a default entry. This affects clients combining those features. The March correction is separate from January's cross-protocol redirect issue.
Inventory netrc use in scheduled jobs and deployment integrations. Keep redirect destinations explicit, update the linked library and verify that authorized requests still reach only their intended endpoint.
Breaches and cyber incidents reported this month
These cases were publicly reported during March 2026. Discovery dates are stated separately where known. The summaries retain the limits of the cited notices: an outage alone does not establish data theft, and exposed records are not automatically a count of people.
| Organization | Public notice | Incident |
|---|---|---|
| Loblaw | 2026-03-10 | Information exposure |
| Stryker | 2026-03-11 | Operational disruption |
Loblaw: contact information and customer session resets (2026-03-10)
On 2026-03-10, Loblaw reported unauthorized access to customer names, phone numbers and email addresses. It logged customers out as a response measure; its initial investigation did not indicate compromise of passwords, health information or credit-card data.
Prepare a controlled way to revoke customer sessions during an incident. Explain the reason for a forced sign-in clearly, and review recovery and support procedures against impersonation using exposed contact information.
Stryker: disruption across a corporate Microsoft environment (2026-03-11)
Stryker's 2026-03-11 filing described a cyber incident causing global disruption to its Microsoft environment and restricting business applications. The filing said the full scope and impact were still being investigated; it did not establish a specific volume of stolen data.
Map which business processes depend on the same identity and collaboration environment. Rehearse an independent way to communicate, receive orders and validate restored access when that environment is unavailable.
Coverage and editorial record
This is a selected review for business websites and hosting, not a complete monthly vulnerability inventory. Each section links to its evidence. Public disclosure or a security release determines the coverage month; a private report date, CVE reservation year or later record edit does not determine that month.
The first edition was prepared on 6 November 2026. Current advisories may contain later corrections, so this article does not claim to reproduce their exact month-end state. No corrections are recorded for this edition. A substantive change will receive a dated note and updated article metadata.
