5 Things Your Web Partner Should Tell You After a Drupal Security Advisory
After a public security advisory, silence from your web partner sounds like nobody checked. A good partner reaches you first, within one business day, and says three things in plain words: whether your Drupal site runs the affected code, what is being done about it, and when it will be finished.
Patching fast is half the job. The other half is the notice, because it's the part of the response IT and digital owners actually see, and the part they repeat to leadership.
Advisories are routine. In the first two weeks of November 2026, Drupal published 48 security advisories for contributed modules and rated 10 of them critical.
Key Takeaways
- A good advisory notice arrives within one business day, before you read about the flaw elsewhere.
- When your site isn't affected, the notice says so and explains how the partner checked, because silence after a public advisory looks like nobody did.
- Notices should be tiered by severity: the most serious issues get a notice and a fix within one business day, and lower risks follow on a slower, agreed timeline.
- Plain words matter. "Your site uses the affected component" informs; "your site is impacted" sounds like a breach.
- Every notice should reach your IT owner, not only your marketing contact, and leave a record you can report upward.
What Should Your Web Partner Tell You After a Drupal Security Advisory?
After a Drupal security advisory, your web partner should tell you three things within one business day: which advisory was published and how serious it is, whether your site runs the affected code, and when the fix will be live. If your site isn't affected, the partner should say so and explain how it checked.
A Drupal security advisory is the Drupal Security Team's public notice of a flaw in Drupal core or a contributed module, with the fixed version to install.
Our View: The First Notice Tests a Partner Before the Patch Does
Our view: the first notice after an advisory tells you more about a partner than the patch does. For most contributed modules, the fix is a version update. The hard part is knowing, within hours, which sites need it and what each client should hear.
The October PHP security release made the point for our own teams. The first hours went to one question: which client sites ran an affected version, and what should each client be told? We covered that work in When a Critical PHP Flaw Lands, Which of Your Websites Are Exposed?
Vardot sells Drupal support and maintenance, so we sit on the partner side of this exchange. Our own security update process follows this standard: the technical team handling the issue writes to clients first, and every message says whether they’re affected and what happens next.
What Does a Good Drupal Advisory Notice Do?
A good Drupal advisory notice does five things. It arrives before the headline, it confirms when your site isn't affected, it's tiered by risk, it uses plain language, and it leaves a record you can report upward.
Who Should Send the First Notice?
One team should own triage and the first notice. When the job falls to whichever account manager sees the headline first, notices arrive late, say different things to different clients, or never arrive.
At Vardot, the first message comes from the technical team doing the work, DevOps for hosting issues and development for the application, with the client’s project owner copied. Each issue has one named owner through to go-live.
The test is simple: the notice should reach you before a news alert, a vendor newsletter or a board member does. That takes someone who watches each Drupal release window and can send a notice without waiting for a meeting.
What Should a Notice Say When Your Site Isn't Affected?
When your site doesn't run the affected code, a good notice says so plainly: we checked, you are not affected, and here is why. After a public advisory, silence looks the same as nobody checking.
The "why" makes the message credible. "Your site doesn't have Commerce Core installed; we confirmed this against your module list today" can be verified. "No action needed" can't.
Writing that within one business day takes a current record of every module and version your site runs. A site inventory is where that record starts. A reply of "we're looking into it" two days later usually means the record doesn't exist.
Should Your Partner Message You About Every Advisory?
No. A good notice system is tiered so it never cries wolf. Messaging on everything would have meant 48 notices in the first two weeks of November 2026, and readers stop opening them before the one that matters. Messaging only when affected leaves silence with two meanings: your site is fine, or nobody looked.
The tiers below follow the response times in our own security update process. Drupal scores each advisory out of 25 and places it on a five-level scale, from Not critical to Highly critical.
Tier | Example | Who hears | When |
|---|---|---|---|
Highly critical, critical, or already exploited | A critical Drupal core release; a flaw Drupal says is under attack | Every client. Affected sites get a patch plan; unaffected sites get a note saying “we checked, you’re not affected” | Within 1 business day; fix live within 1 business day |
Moderately critical | A module advisory with limited impact | Clients whose sites run it, with a patch plan | Within 1 business day; fix live within 5 business days |
Less critical | A low-risk advisory | Clients whose sites run it | Fix in the next scheduled deployment |
Agree the tiers in writing. It takes effort up front, and it's the only setup where silence means something.
What Words Should an Advisory Notice Use?
An advisory notice should use words a non-technical reader can repeat to leadership without changing their meaning. "Impacted" is the word to drop: to an executive, it reads as "breached."
A site that runs vulnerable code is exposed. A site where someone used the flaw is compromised. Leadership needs to know which one the notice means, and the plain-language table below pairs common phrases with clearer ones.
Instead of | Say |
|---|---|
"Your site is impacted by SA-CONTRIB-2026-254." | "Your site uses Commerce Core, the module this advisory covers. We are updating it tonight and will confirm when it's done." |
"We're looking into it." | "We’ve reviewed the advisory, and your site needs this update. After testing on staging, it goes live Thursday at 09:00 UTC, with up to 10 minutes of downtime." |
"No action required." | "Your site doesn't use the affected module. We confirmed this against your module list today." |
Where Should the Record of Each Advisory Live?
Every notice should leave a record you can report upward. An email blast can land in spam or leave with the person who received it. Keep one thread per security issue, in your project tool or a single email thread, from the first notice to the go-live confirmation.
The monthly or quarterly report should then list each advisory checked, whether it applied, and when the fix went live.
Who in Your Organization Should Receive the Notice?
Advisory notices should go to the person who owns your site's risk, usually an IT or digital lead, not only the marketing contact who requests content changes. A marketing contact can't approve an emergency change or answer an auditor.
Name a security contact and a backup who can approve urgent deployments, and expect one named owner per issue from your partner in return. A shared address keeps notices flowing through holidays and staff changes.
How Often Do Drupal Security Advisories Arrive?
Drupal security advisories arrive on a published schedule. The Drupal Security Team's release timing policy sets a window every Wednesday for contributed modules, the add-ons built by the community, and one Wednesday a month, usually the third, for Drupal core. Releases land between 16:00 and 22:00 UTC, which is 11:00 to 17:00 US Eastern in winter.
Volume is the harder part. Drupal.org lists 24 contributed-module advisories in each of the first two November windows. Nine were rated critical on November 4 and one on November 11, and none had public exploit code at release. Each advisory covers one module, so most of them won't touch your site.
On November 18, the monthly core window brought two more: a critical remote code execution fix and a moderately critical one.
How Fast Do Attackers Move After a Drupal Flaw Is Disclosed?
Attackers move within days when they move at all. Rapid7's Q3 2026 threat report found that exploitation came three days after disclosure on average, and 71% of it within a week. That figure covers flaws attackers chose to use; most advisories never lead to an attack.
October showed the worst case. When Drupal published its Commerce Core advisory on October 28, 2026, it rated the flaw highly critical and said attackers were already using it.
What Should Your Support Contract Say About Security Releases?
A support contract should treat security releases as their own category, with six terms. Outage clauses don't cover them, because a site with a known flaw is still up.
- Named owners on both sides. Who watches the Wednesday release windows for the partner, who receives notices for you, and who covers for each.
- Notice tiers and records. Which risk levels trigger a notice within one business day, which wait for a scheduled update, and where each notice is logged.
- Response times. Time to first notice and time to deploy, set per severity. Our own targets: highly critical and critical fixes live within 1 business day, moderately critical within 5.
- Emergency change approval. Who can approve an out-of-hours deployment, including during a change freeze.
- Cost. Whether security updates sit inside the retainer or are billed per event, and what out-of-hours work costs.
- End of life. How fast the partner tells you when an advisory has no fix for your version, what interim protection it applies, and when the upgrade scope follows.
This standard has a run cost: someone has to watch a six-hour window every Wednesday. Expect a partner to price that work, and ask how it's staffed.
For the wider contract, see our guides to what a 24/7 support SLA should cover and proactive Drupal support beyond patching.
Which Four Questions Show Whether Your Partner Is Ready?
Four questions show whether your current partner is ready for the next Drupal security advisory. Send them in one email; under each is what a prepared partner says.
- Who watched last Wednesday's security window? A prepared partner gives a name and a backup. "The team" means nobody is assigned.
- Which November advisories affected our site? A prepared partner answers from a record, within a day. A reply that takes a week usually means someone checked by hand.
- What did you fix after the last advisory that applied to us? A prepared partner names the advisory, the version, and the deployment date. "Updates applied" can't be verified.
- How fast must you deploy a critical security fix under our contract? A prepared partner quotes the clause. If the contract only covers outages, a critical fix can wait for the next maintenance cycle.
If all four replies hold up, keep them as your record. If three or four fall short, advisory response is unmanaged: raise it now, and before December 9, 2026, if your site still runs Drupal 10. Our Drupal 10 end of life decision calendar covers the options.
Not sure your contract covers security releases?
Vardot’s support team will review your support agreement against the six security-release terms and show you where the gaps are.
Book a support contract review
What Should You Hear on the Day of a Critical Release?
For the most serious issues, the Drupal Security Team warns site owners with a public service announcement (PSA). On Monday, November 16, 2026, it announced critical core security releases for Wednesday, November 18, between 17:00 and 21:00 UTC, warned that at least one flaw could be exploited by anonymous users, and advised sites to move to the latest patch release beforehand. The release, SA-CORE-2026-017, fixed a critical remote code execution flaw rated 18 out of 25.
A pre-announcement gives a partner two days to prepare, so the fix can go in within hours of its release. On release day, the notice you receive should cover four points:
- The advisory ID and risk level.
- Whether your site is affected, and how that was checked.
- The fix applied, and when it went live.
- The version now running, what was tested, and whether logs showed any attempt to use the flaw.
What Should You Do Next?
Send your web partner the four readiness questions this week. How long the replies take matters as much as what they say.
If the replies show gaps, compare your support agreement with the six security-release terms in this article. Book a support contract review, and Vardot's support team will go through that agreement with you. See our Drupal support and maintenance service.