A university rarely has one Drupal site. It has the main site, the admissions site, a site for each college, research center sites, and a long tail of department sites built over the years by whoever had the budget. Many school districts look the same at a smaller scale: a district site and a site for every school.
Starting in 2027, each Drupal minor version gets eight months of security support instead of twelve. That means two upgrades a year, and the count that matters is not one site. It is every site.
Where this comes from. The Drupal Security Team's announcement of November 2, 2026 (PSA-2026-11-02) and Drupal's core release schedule, read directly.
The Good News Is the Calendar
Drupal releases new minor versions in June and December. Under the new rules, the previous version stays covered for about two months after each release. Lay that over an academic year and it lines up better than most IT schedules do:
- June release, summer upgrade. Drupal 11.6 and 12.1 are scheduled for June 2027. The December versions stay covered until August 2027. That is a summer upgrade window.
- December release, winter break upgrade. The December 2027 releases arrive as the fall term ends. The June versions stay covered until February 2028. That is a winter break upgrade window.
Two windows a year that fall when classes are out. The schedule only works if someone puts both on the institution's calendar now.
The Near-Term Dates
- Drupal 10.6 and 11.3. Security support ends the week of December 7, 2026. Drupal 10 reaches end of life on December 9.
- Drupal 11.4. Supported until April 21, 2027, in the middle of the spring term.
Any site on 11.4 needs to move to 11.5 or 12.0 before late April. For most campuses, spring break is the realistic window.
Where Campuses Get Caught
- Orphaned sites. Department and center sites that were built once and never handed to anyone. They are often on older versions, and nobody notices until a scan or an incident finds them.
- Split ownership. If central IT runs the main site and colleges run their own, the upgrade calendar has to reach every owner, or the oldest site sets the institution's risk.
- Module sprawl. Every upgrade multiplies by every module on every site. Campus sites often depend on single sign-on, directory and integration modules, and those modules get security advisories too.
- Vendor-built sites. Admissions, athletics and alumni sites are often built and hosted by an outside firm on its own contract. Those contracts were written for the old schedule too. Ask each vendor, in writing, how they will keep your site on a supported version under the new one.
The Accessibility Date on Top
A public university that is part of its state takes the state's population under the ADA Title II web rule, so it is on the April 26, 2027 date, five days after Drupal 11.4 loses support. A pending lawsuit asks a federal court to undo the one-year extension behind that date, which would make it earlier. Independent school districts use their own Census population, so a large district is on the same date. Accessibility work and version upgrades are usually done by the same people. Plan them as one schedule.
What to Do This Term
- Count the sites. List every Drupal site the institution runs, its version and its owner. If you cannot list them, start there.
- Book the windows. Put the June to August and December to February windows on the IT calendar for 2027.
- Retire what you can. Sites nobody uses can be archived or shut down. Fewer sites means fewer upgrades.
- Consolidate the rest. Move the sites that matter most onto a shared, maintained setup instead of a dozen separate builds.
Keep Your Drupal Site on a Supported Version
Our partnership plans give you a team that tracks Drupal core and module security releases, applies the updates, and schedules the two minor upgrades a year so your site does not run on an unsupported version. Every plan is a set number of hours each month, so security updates, upgrades and improvements come out of the same predictable budget.