Selected events and fix thresholds
This retrospective covers 2026-05-01 to 2026-05-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-05-04 | Apache HTTP Server | CVE-2026-23918 | 2.4.67 |
| 2026-05-13 | NGINX | CVE-2026-42945 / CVE-2026-9256 | 1.31.0 / 1.30.1 / 1.31.1 / 1.30.2 |
| 2026-05-04 | Apache HTTP Server | CVE-2026-33006 | 2.4.67 |
Apache: HTTP/2 double free in 2.4.66 (CVE-2026-23918)
Apache identifies a double-free weakness with possible code execution in the HTTP/2 implementation of version 2.4.66. Version 2.4.67 contains the fix. The stated affected version is specific, so a version inventory matters before assigning the work.
Identify the httpd package and HTTP/2 module in each hosting environment. Agree the update and reload, then test virtual hosts, certificates and application traffic.
NGINX: two rewrite fixes during May (CVE-2026-42945 / CVE-2026-9256)
Two separate rewrite-module buffer overflows were disclosed in May. They depend on particular regular-expression captures and directive combinations. Crashes are possible; code execution requires additional conditions involving ASLR. The later advisory on 22 May requires newer fixes than the 13 May issue.
For CVE-2026-42945 the OSS thresholds are 1.31.0 / 1.30.1; for CVE-2026-9256 they are 1.31.1 / 1.30.2. Review both notices, including the Plus package mapping, and test redirects with application owners.
Apache: Digest authentication bypass (CVE-2026-33006)
A timing attack against mod_auth_digest can bypass Digest authentication. Apache lists affected releases through 2.4.66 and recommends 2.4.67. The relevant boundary is an area protected by this Apache module, which is separate from an application's own login implementation.
Map directories and virtual hosts using mod_auth_digest. Apply the supported patched package and check that protected pages reject unauthenticated access after reload.
Breaches and cyber incidents reported this month
These cases were publicly reported during May 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 |
|---|---|---|
| Instructure / Canvas | 2026-05-08 | Information exposure |
| Carnival Corporation | 2026-05-27 | Information exposure |
Canvas: exposed user data and interrupted learning (2026-05-08)
In its 2026-05-08 statement, Instructure identified exposed usernames, email addresses, course and enrollment information and messages. It reported that core learning data and credentials were not compromised. Its incident timeline records initial detection on April 29 and another attack on May 7.
For a business-critical SaaS platform, agree how incident notices reach the responsible person and how work continues during an outage. Keep an inventory of integrations and administrative access that may need review when a supplier reports a breach.
Carnival: a compromised employee account and personal information (2026-05-27)
On 2026-05-27, Carnival announced notifications about an April incident. It said social engineering enabled access through an employee account, detected on 2026-04-14, and that certain personal information was accessed unlawfully. The attack date and public notification month were different.
Review verification procedures for employee access recovery and support requests. Restrict access to customer records by job role and prepare a way to identify affected people from logs without relying on an unverified attacker-provided record count.
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.
