Drupal Planet

Security advisories: Drupal core - Moderately critical - Gadget chain - SA-CORE-2026-018

Project: Drupal coreProject machine name: drupalDate: 2026-November-18Security risk: Moderately critical 14 ∕ 25 AC:Complex/A:Admin/CI:All/II:All/E:Theoretical/TD:UncommonVulnerability: Gadget chainAffected versions: <10.6.22 || >=11.0.0 <11.3.22 || >=11.4.0 <11.4.13CVE IDs: CVE-2026-132166Description: 

Drupal core contains a chain of methods that could be exploitable when an insecure deserialization vulnerability exists on the site. This so-called "gadget chain" presents no direct threat, but is a vector that can be used to achieve remote code execution if the application deserializes untrusted data due to another vulnerability.

This issue is not directly exploitable.

This issue is mitigated by the fact that in order for it to be exploitable, a separate vulnerability must be present to allow an attacker to pass unsafe input to unserialize().

Solution: 

Install the latest version:

Drupal 11

  • If you use Drupal 11.4.x, update to Drupal 11.4.13.
  • If you use Drupal 11.3.x, update to Drupal 11.3.22.
  • Drupal 11.2.x and below are end-of-life and do not receive security coverage.

Drupal 10

  • If you use Drupal 10.6.x, update to Drupal 10.6.22.
  • Drupal 10.5.x and below are end-of-life and do not receive security coverage.

Drupal 8 and Drupal 9 have both reached end-of-life.

Reported By: Fixed By: Coordinated By: 

Security advisories: Drupal core - Critical - Remote code execution - SA-CORE-2026-017

Project: Drupal coreProject machine name: drupalDate: 2026-November-18Security risk: Critical 18 ∕ 25 AC:Complex/A:None/CI:All/II:All/E:Proof/TD:UncommonVulnerability: Remote code executionAffected versions: <10.6.22 || >=11.0.0 <11.3.22 || >=11.4.0 <11.4.13CVE IDs: CVE-2026-132165Description: 

Drupal core ships with an install.php file for installing Drupal core.

Under specific conditions, an attacker can use the installer to attempt to reinstall Drupal. This can lead to a site takeover or remote code execution.

Some exploit paths are mitigated if the web server cannot write to or change permissions on settings.php. In addition to upgrading, the Drupal Security Team recommends securing the Drupal installer after installation.

Discovered by Anthropic's OSS Scanner, as vulnerability ANT-2026-GMRPK0BU.

Drupal Steward protection:

This issue is being protected by Drupal Steward. Sites that use Drupal Steward are already protected from some known attack vectors, but the protection offered will not cover all possible exploits. Sites should upgrade in the near future in case additional attack vectors are discovered.

Solution: 

Install the latest version:

Drupal 11

  • If you use Drupal 11.4.x, update to Drupal 11.4.13.
  • If you use Drupal 11.3.x, update to Drupal 11.3.22.
  • Drupal 11.2.x and below are end-of-life and do not receive security coverage.

Drupal 10

  • If you use Drupal 10.6.x, update to Drupal 10.6.22.
  • Drupal 10.5.x and below are end-of-life and do not receive security coverage.

Drupal 8 and Drupal 9 have both reached end-of-life.

If you cannot upgrade immediately:

Follow the instructions for securing the Drupal installer to protect your site from attacks.

Reported By: Fixed By: Coordinated By: 

Tag1 Insights: Inside the Pyramid: The Ideal Shape for Drupal’s Test Suite

Take Away Francesco Placella, Tag1 Senior Architect and Technical Lead, opens a four-part series on why Drupal’s test suite has grown slow and expensive to run. This post looks at how the suite got its current shape and why the Test Pyramid is a better target. The series comes from his DrupalCon Rotterdam 2026 session and supports the initiative to adopt the Test Pyramid approach in Drupal core, which is looking for contributors. The Ideal Shape

As we touched on in Speed Up Your Testing with Deuteros, the Drupal test suite is not in an ideal shape. If we consider the distribution of tests among the various Drupal test types (UnitTestCase, KernelTestBase, BrowserTestBase, WebDriverTestBase, and BuildTestBase), we quickly realize that, instead of resembling the Test Pyramid, which relies on a wide majority of lightning-fast Unit tests, we are currently stuck with what I call the Test Spinning Birthday Cake:

Figure 1: The Test Spinning Birthday Cake.
Source: *Test.php files in core/tests and in core modules, profiles, themes and recipes; abstract classes left out. Nightwatch not included.

Running our test suite ended up being either slow or very expensive: as a matter of fact, a significant slice of the Drupal Association’s budget currently goes into running CI tests on drupal.org.

How Fast?

For anyone wondering how much faster UnitTestCase tests are, here is how long it took 1,000 iterations of the same test code to complete, according to the Deuteros benchmarks:

  • UnitTestCase + PHPUnit mocks: <1s
  • UnitTestCase + Prophecy API mocks: <0.5s
  • KernelTestBase + Entity objects: ~12 minutes
Redundant Redundancy

The main reason for this inefficiency is redundancy: many functional or kernel tests end up covering overlapping functionality, so we test the same code paths over and over.

To make matters worse, we are also dealing with inconsistent granularity: next to a functional test covering an entire form, you can find another functional test only checking that one option of a selector in that form behaves correctly: test coverage for a single bug fix next to that of an entire feature.

This is what I would call explicit redundancy.

However, we also have implicit redundancy, which may come in a few flavors:

  • Testing at the wrong level, meaning much higher than the code we actually care about. Say we exercise our code path through a functional test, very far from the class we want to test: that implicitly tests every step between Drupal’s bootstrap and our code, that is, the entire stack.
  • Enabling modules just to autoload classes. All Drupal tests use a bootstrap script that autoloads the classes of every module, so you can just use them in your test. Enabling a module just to autoload its code exercises the whole module installation pipeline, every time the test runs, for no reason, because that is not what your test is about.
  • Needlessly relying on persistence. It is not uncommon to find tests where an entity is saved even though it is only being manipulated as a data object used to pass information around. That alone is a reason people pick kernel tests and, if you do not need persistence, there are much more performant options.

As a consequence, readability suffers as well, since the test’s assertions and expectations are often lost among several lines of setup code or other preliminary steps, as those kinds of tests usually require a more complex test environment.

The bottom line is that, speed and costs aside, DX and maintainability are not exactly ideal either.

How Did We Get Here?

Back when we added automated testing, we introduced a test gate mandating test coverage for any change landing in core. No matter whether you were dealing with a brand-new feature or a tiny bug fix, everything had to get test coverage. However, the guidelines stopped there: there was no clear direction about which kind of test to write each time. So people would either pick the route they were most familiar with or piggyback on an existing test.

That is not bad in itself, but it depends on which tests are available. By now we have a lot of tests inherited from the Drupal 7 days, hence an abundance of functional tests, which are among the slowest to run. And many new tests are functional tests as well, for similar reasons.

Right now, even our AI best practices will not encourage you to write Unit tests. Their claim:

“Unit tests, at least in Drupal, are the least useful kind of tests.”

Harsh, but that is our current reality, and it is going to be reinforced one AI-generated test at a time.

As far as I can tell, one of the main reasons Unit tests are seen as the least useful is that most Drupal code manipulates entities, and entities are very hard to Unit-test because they bring a lot of baggage. The moment you try to instantiate one in a UnitTestCase test, you find yourself setting up test doubles for half of the Entity system.

Francesco presented the Test Pyramid at DrupalCon Rotterdam 2026. Watch the session > The Silver Bullet

Figure 2: The Test Pyramid.

I believe the Test Pyramid can help us address the Drupal test suite’s performance issues, by letting us implement most of the coverage via Unit tests, and only rely on kernel and functional tests for very narrow and specific use cases: for instance, to ensure subsystems are correctly wired and that critical scenarios are working properly.

Aside from Speed, if we adopt the Test Pyramid we get more:

  • Breadth. If your class method has an if branch, you have two cases to test. Two class methods with an if each, four cases, and so on. Test your classes individually and you are testing two cases at a time. Let them combine and the number of code paths explodes: by the time you get to the top, it is impossible to exercise them all. That is where we are now: there is no way to have exhaustive coverage through the current approach, while the Pyramid would give us much finer-grained coverage at the bottom.
  • Explicitness. Ever tried debugging a functional test? Most of the time you get an error that doesn’t tell you which line to look at. You navigate the codebase, exercise your intuition, maybe spin up a debugger and step through the test at hand, and after a while you may track the issue down to a class. If you were Unit-testing that class, its test would fail and you would know instantly where to look.

Push test coverage down whenever you can and you get all of these advantages, thus improving DX as well. Combine that with clear guidelines on how to shape your module’s test suite and Maintainability improves significantly.

To make a long story short, in my opinion this is the shape we should aspire to, the Test Squeezed Skyscraper:

Figure 3: The Test Squeezed Skyscraper, an illustrative target distribution applied to Drupal core’s 3,843 test classes.

We should aim for something with a very wide base and much thinner upper layers. How much we can actually squeeze remains to be seen, but that is the ideal goal.

The Trap

Did you notice any resemblance between the Pyramid and the Squeezed Skyscraper? They look very similar, but this similarity hides a trap: in practice there is no direct mapping between the layers of our Skyscraper, that is, Drupal’s test types, and the levels of the Pyramid. Sure, they are correlated, but there is no hard rule enforcing a mapping between them. In fact, you can:

  • Unit-test an individual form builder class in UnitTestCase, even if it is about the UI.
  • Write a database Integration test based on UnitTestCase, not a kernel test.
  • Test a full request/response cycle End-To-End through a kernel test, not a functional test. This is a recent, very exciting addition.
  • Unit-test an object through a functional test - joking, that would take us back to Drupal 7.

To sum up, test levels are not the same as test types. Test types are tools at our disposal for providing coverage. Test levels define the scope of a test:

  • End-To-End tests exercise your codebase through its entire scope, which for Drupal means a request/response cycle. They should be the bare minimum needed to cover critical scenarios, like the login flow.
  • Integration tests exercise subsystems together, often crossing the process boundary: think of database queries, file system access, API requests. You want as many of these tests as needed to ensure your code is wired together properly.
  • Unit tests cover individual behaviors of your codebase, typically targeting a single class. If your code is object-oriented and organized properly, you can do a lot with Unit tests alone.

These days the default assumption is that when implementing an Integration test, we need a kernel test, and when testing something at the UI level, we need a functional test. In a way, I have been suggesting this myself. This doesn’t have to be the case.

I think the goal should be to widen the Skyscraper’s base: push down towards it as many tests as we can. If we can do an Integration test using UnitTestCase, great. That doesn’t mean breaking the rules and using a Unit test where an Integration test is called for. It means we can get a fast test while still getting the coverage we were aiming for.

Up Next

In the next post, I’ll cover how to get there and the principles behind the guidelines I’m proposing.

Want a faster, leaner test suite for your Drupal project? Talk to our team.

Aten Design Group: Comparing Search Options in Drupal

Comparing Search Options in Drupal Ella Toupin Tue, 11/17/2026 - 11:37 Drupal

Search is one of the most important features of a content-heavy website. Whether visitors are looking for university programs, government services, library resources, or documentation, the ability to find relevant content quickly can make or break their experience.

Drupal offers several approaches to search, ranging from basic database-backed solutions to dedicated search engines, AI-powered search, and third-party platforms. Each comes with different capabilities, costs, and maintenance requirements.

Let's look at the primary options, their advantages and limitations, and where each makes the most sense.

Drupal's native search optionsDrupal Core Search

Drupal historically included a Search module that indexed website content directly in its database. It provided basic keyword searching without requiring additional services.

Benefits: Simple to configure, no external infrastructure, and minimal setup.

Drawbacks: Limited control over relevance, filtering, and advanced search functionality. It is not particularly well suited to large or complex content collections.

While Drupal Core Search was deprecated in Drupal 11.5, and removed altogether from Drupal 12, the functionality continues as a contributed module.

Best for: Existing Drupal sites with straightforward search requirements. For new implementations, Search API is generally a better starting point.

Example: A municipal website search demonstrates a straightforward approach to helping residents find public information and services.

Search API with Database Search

Search API is Drupal's most widely used framework for building customized search experiences. It allows developers to define what content gets indexed, configure searchable fields, and integrate results with Drupal Views.

Importantly, Search API is not a search engine itself. It connects Drupal to different search backends.

Its bundled Database Search backend stores the search index in Drupal's existing database, eliminating the need for additional infrastructure.

Benefits: Flexible indexing, control over searchable fields, integration with Views, and support for features such as faceted filtering through additional modules. It can also index more than just Drupal nodes.

Drawbacks: Database-backed searching has limitations around relevance tuning, language processing, and performance at larger scales. Advanced capabilities depend on the backend being used.

Best for: Small to medium-sized Drupal websites that need more control than Core Search provides without the overhead of a dedicated search server.

Example: A content-focused search with page-type filtering demonstrates how a straightforward search interface can help visitors narrow results by content type without an overly complicated experience.

Dedicated search enginesSearch API with Apache Solr

Apache Solr is a dedicated, open-source search engine commonly used with Drupal through the Search API Solr module.

Solr moves indexing and searching into a separate service, providing more advanced capabilities than traditional database searching.

For content-heavy Drupal implementations, Search API with Solr is often a strong starting point. It provides considerable flexibility without requiring a proprietary search platform.

Benefits: Strong relevance tuning, faceted navigation, multilingual searching, stemming, synonyms, and the ability to search large collections efficiently. Additional integrations can also support indexing PDFs and other documents.

Drawbacks: Requires a separate Solr service and additional configuration. Index management, search configuration, monitoring, and infrastructure all introduce ongoing maintenance considerations.

Fortunately, several Drupal hosting providers offer managed Solr services, reducing the operational burden.

Best for: Larger Drupal websites with substantial content libraries, complex filters, multilingual requirements, or sophisticated relevance needs.

Example: A large-scale website search with content-type filtering demonstrates how visitors can search across thousands of pages, events, articles, and other content types. Faceted filters help narrow results without requiring separate search interfaces for each content collection.

Elasticsearch and OpenSearch

Elasticsearch and OpenSearch are distributed search engines that offer many capabilities comparable to Solr.

Both can integrate with Drupal through Search API backend modules, though they are separate products with different APIs and licensing models.

Benefits: Powerful full-text search, filtering, scalable indexing, and sophisticated query capabilities. They can also be useful when search extends beyond Drupal into other applications or centralized data platforms.

Drawbacks: Like Solr, they require additional infrastructure and technical expertise. Drupal integration modules vary in maturity and compatibility, making their long-term support an important consideration.

Best for: Organizations already using Elasticsearch or OpenSearch, or projects that need a search platform shared across multiple applications.

For a standalone Drupal website, Solr's mature integration may make it the more straightforward choice. Elasticsearch and OpenSearch become particularly attractive when they align with an organization's existing infrastructure.

Example: A healthcare website search illustrates how search can support content discovery across treatments, physicians, research, and patient information.

AI-powered search in DrupalDrupal AI Search

The contributed AI Search module brings semantic search capabilities to Drupal through Search API.

Traditional keyword search primarily looks for matching terms. Semantic search uses vector embeddings to identify content related to the meaning of a query, even when the wording differs.

For example, someone searching for "How do I get help paying for college?" might receive relevant financial aid information without needing to search for the exact phrase "financial aid."

AI Search generates embeddings from Drupal content and stores them in a compatible vector database, such as Pinecone, Qdrant, or Milvus. It also supports hybrid approaches that combine semantic search with traditional keyword results from backends such as Solr.

Benefits: Natural-language searching, improved discovery of conceptually related content, and integration with Drupal's existing Search API framework. It can also provide the retrieval foundation for AI assistants and question-answering experiences.

Drawbacks: Requires additional services for generating and storing embeddings, introduces processing and infrastructure costs, and requires careful evaluation of result quality. The contributed module is also relatively new, with its available releases still in alpha as of November 2026.

Best for: Websites where visitors frequently search using questions or imprecise terminology, or organizations exploring conversational search and AI-assisted content discovery.

One important distinction: semantic search does not automatically mean AI-generated answers. Drupal AI Search primarily retrieves relevant content. Producing conversational responses or summaries requires additional functionality, often using retrieval-augmented generation (RAG).

External and managed search servicesGoogle Programmable Search Engine

Google Programmable Search Engine allows websites to embed a Google-powered search experience without maintaining their own search index.

Rather than indexing Drupal entities directly, it relies on Google's search infrastructure to discover and retrieve publicly accessible pages.

Benefits: Relatively simple implementation, minimal infrastructure requirements, and the ability to search across multiple websites.

Drawbacks: Less control over indexing, ranking, and result presentation than a dedicated search platform. Content freshness depends on Google's indexing, and advertising, branding, and customization options vary by offering.

Google also announced changes in 2026. Its site-specific Search Element continues to support up to 50 designated domains, while users of the Custom Search JSON API and certain broader web-search configurations must transition by January 1, 2027.

Best for: Websites with relatively simple public-content search requirements, particularly when searching across multiple domains is desirable and customization is not a priority.

Example: A higher education website using Google-powered search demonstrates how an institution can incorporate an external search engine into its website without maintaining a separate search index.

Cludo and other managed search platforms

Cludo is a commercial search platform designed specifically for website search. Unlike Drupal-specific search backends, it can crawl and index content across multiple websites regardless of the underlying CMS.

Cludo also provides tools for managing search relevance, promoting important results, and analyzing visitor search behavior.

Benefits: Managed infrastructure, cross-site search, search analytics, and administrative tools for adjusting relevance. It can index publicly accessible pages and documents, with APIs available for more specialized integrations.

Drawbacks: Subscription costs, reliance on an external vendor, and potentially less direct integration with Drupal's structured content and access controls. Crawl configuration and indexing frequency require attention.

Best for: Large organizations managing multiple websites or content platforms, particularly when a managed solution and built-in search analytics are priorities.

Example: A municipal website search powered by a managed search platform illustrates how an external search service can provide a dedicated search experience without relying on Drupal's native search infrastructure.

Cludo is not the only option in this category. Platforms such as SearchStax and Algolia also provide managed search capabilities, although their approaches to Drupal integration, indexing, and search administration differ.

How should you choose?

The right solution depends on more than content volume. Before selecting a search platform, consider a few practical questions:

  • What needs to be searchable? Drupal content, PDFs, multiple websites, external databases, or some combination?
  • How sophisticated should search be? Basic keyword matching may suffice, while extensive content collections may benefit from facets, autocomplete, synonyms, and customized ranking.
  • Who will configure and maintain search? Some solutions rely heavily on developer configuration, while others provide interfaces for adjusting relevance and analyzing search behavior.
  • What infrastructure and budget are available? Open-source software avoids licensing fees but still requires development and operational support.
  • Are there access restrictions? Search must respect content permissions, particularly when indexing protected or unpublished information.

It's also worth considering how search will be evaluated after launch. Popular queries, searches returning no results, and the pages visitors actually select can reveal problems with content organization as well as search configuration.

A more powerful search engine cannot compensate for poorly structured, outdated, or duplicated content.

Final thoughts

For smaller Drupal websites, Search API with Database Search is often sufficient. As content volume and search requirements grow, Search API with Solr provides a mature and flexible approach.

Elasticsearch and OpenSearch are compelling alternatives when they align with existing technical infrastructure. Google Programmable Search remains an option for relatively simple public-site searching, while managed platforms such as Cludo can be especially useful for organizations managing content across multiple websites.

No single approach is right for every project.

The goal isn't to implement the most sophisticated search engine available. It's to select a solution that makes content easier to find, can be maintained over time, and gives the organization appropriate control over the search experience.

Philip Stier

Drupal Association blog: In the Open: Telling Drupal’s story together

In the Open is a weekly series from Drupal Association Interim CEO Tiffany Farriss, sharing what she is hearing across the Drupal community and where the Association is headed. In this episode: why closing the gap between what Drupal can do and what the market knows is urgent, how the new Drupal advocacy program recognizes advocacy with contribution credit, and how it connects to the new Drupal Certified program.

“Advocacy has always happened in our community, but it’s really been very scattered and unrecognized.”

The following is a transcript of Tiffany’s remarks, lightly edited for readability.

Closing the perception gap

Drupal is light years ahead of its reputation. Our software has improved much faster than our story, which leaves a real gap between what modern Drupal can actually do, especially around AI and Drupal CMS, and what the broader market realizes.

I’m Tiffany Farriss, the Interim CEO of the Drupal Association, and this is In the Open, my regular update on what’s happening at the Association as we navigate a year of change.

Closing the perception gap is urgent. People increasingly learn about technology from AI assistants, and those assistants learn from the open web. When governments, universities, and enterprises run serious platforms on Drupal quietly without publishing about it, the public record falls behind. Every genuine story about Drupal on LinkedIn, on Reddit, YouTube, or any sort of tech blog improves what both people and AI systems know about our project.

You can’t buy that kind of credibility. It comes from real people sharing results that are verifiable and accessible to anyone.

The Drupal advocacy program

That’s why we launched the Drupal advocacy program. Advocacy has always happened in our community, but it’s really been very scattered and unrecognized. Now, helping people understand what Drupal can do earns contribution credit through the exact same system that recognizes code and other community contributions.

Adoption and education are crucial parts of sustaining open source. A digital public good creates the most value when people actually know what it can do and use it.

Four rules for advocacy

To keep our credit meaningful, we set four clear rules.

First, translation, not amplification. Sharing someone else’s post is fine, but the highest value work comes from your own perspective, your industry, your language, speaking to your clients, what you actually know.

Two, crowd surf, not AstroTurf. It’s not about repeating someone else’s words, it’s about what you’ve done, your experience. And your organization’s work is excellent evidence, as long as you’re telling Drupal’s story and not just pitching your own services. That’s great, too. It’s just not Drupal advocacy.

Three, proof over claims. Back it up. Whatever you say needs to be something that people can check, whether it’s a live site or a working demo or a recorded talk or other data. Let’s make it provable.

Four, quality and reach over volume. Ten super thoughtful pieces that reach 3,000 people outside of our community does way more for Drupal than 30 posts that reach the same 300 insiders.

What we saw in month one

We’re already seeing what happens when people put this into practice. Thanks to Ryan Witcombe and the DA marketing team standing up this pilot, we reviewed 264 pieces of advocacy from nearly 150 contributors around the globe, in seven languages, in just one month alone.

We’ve awarded 2,400 contribution credits in that first month to people like John Money, Kai Gertz and Tojio ai Gertz, who took live AI demos onto stages at non-Drupal conferences. There’s Ivan Zugec, who published over 100 videos helping newcomers learn about Drupal. And Mike Anello, doing what Mike Anello always does and has done for years. He uses his platform to spotlight and amplify the work of fellow community members.

You can see all 15 standout contributors from month one in the link below.

Advocacy and the new Drupal Certified program

Formalizing this advocacy also directly connects to how we’re evolving the Drupal Certified Partner program into the new Drupal Certified program. Instead of a single weighted score, organization profiles will now show three distinct ways that organizations contribute: maker, patron, and advocate.

Drupal is a registered digital public good, and the code is free forever. But running and sustaining the project, for everything that we do beyond the code itself, takes sustained, ongoing operational resources. From the DA, it’s roughly $10 per site every year. That doesn’t count the roughly $30 or more in community time for ongoing roles like core release management, security coordination, and testing.

The new Drupal Certified program is a public trust registry that recognizes organizations that participate in our Drupal ecosystem in a sustainable way, shouldering their fair share of that ongoing operational load, either directly, or by sponsoring it through the DA, or directly to the community members who already do the work.

Publishing verified sector services and contributions as structured data makes certified organizations easier for AI answer engines and buyers alike to find and to cite. Longer term, it will give procurement teams a simple public ledger to verify whether and how a vendor actually participates in the open source ecosystem for the software solutions they’re trying to sell.

It’s a message of strength. Drupal is a digital public good, and organizations should choose vendors who sustain it.

How to take part

To keep our momentum going, the Association has set quarterly themes, and on-theme work earns double credit. Our Rotterdam theme is now wrapped up, and the next theme is around our Drupal 12 launch in December, though good Drupal advocacy qualifies year-round. Anything you publish about Drupal in 2026 still counts.

You can submit your work in about a minute at drupal.org/advocacy, or through the workflow in our Promote Drupal channel on Drupal Slack. We award credits monthly, alongside a roundup of the month’s best work. So contributors get seen, not just scored, and we’re going to be celebrating standout work that’s been created as a part of this pilot at DrupalCon Orlando in 2027.

Stewarded open source takes more than just code. It takes infrastructure, it takes security, it takes release management, events, and advocacy, all working together to make sure that the right information is available at the right time to those who are looking for it.

No single organization can educate the market alone. When the Association does the shared groundwork once and recognizes the people who step up, we amplify those individual stories into a network effect. More people see what Drupal can do, more organizations choose it, and more contributors join in to keep our commons strong.

So thank you for helping the world see what Drupal can do, and I’ll see you next week, in the open.

Follow the conversation

New episodes of In the Open publish each week. Subscribe on the Drupal Association YouTube channel to follow along.

With thanks to Stephen Cross of Second Signal Media for producing this series.

Peoples Blog: Drupal 6 and 7 Websites: What Drupal 12 Means for Your Business Upgrade Plans

A business website may continue working for years without requiring major changes. Customers can visit pages, read information, submit enquiries and access services. From the outside, everything may appear normal. However, the technology supporting a website also evolves, and businesses that continue using older platforms may eventually face challenges when they need improvements, maintenance or new features.

Nonprofit Drupal posts: November 2026 Drupal for Nonprofits Chat

Join us THURSDAY, November 19 at 1pm ET / 10am PT, for our regularly scheduled call to chat about all things Drupal and nonprofits. (Convert to your local time zone.)

We don't have anything specific on the agenda this month, so we'll have plenty of time to discuss anything that's on our minds at the intersection of Drupal and nonprofits. Got something specific you want to talk about? Feel free to share ahead of time in our collaborative Google document at https://nten.org/drupal/notes!

All nonprofit Drupal devs and users, regardless of experience level, are always welcome on this call.

This free call is sponsored by NTEN.org and open to everyone.

Information on joining the meeting can be found in our collaborative Google document.

The Drop Times: When Search Answers Without a Click

Google Search is getting better at answering questions, but what happens when the answer is enough and nobody visits the website behind it? On 12 November, Google introduced Gemini 4 Hydrogen to Search, promising a better grasp of complicated questions, richer results and links to more sources. That sounds useful for people searching. For the publishers supplying those answers, the harder question is what happens after their work appears in a result.

There is reason to ask. Pew Research Center found that users clicked a traditional search result in 8% of visits when an AI summary appeared, compared with 15% when it did not. Those figures come from March 2025, well before Hydrogen, so they cannot tell us what the new model will do. Google has offered a different perspective: it says overall organic clicks from Search have remained relatively stable and the visits it sends are more engaged. The two accounts measure different things, and publishers have to live with that uncertainty.

For years, a useful search result was often a route to a website. Now a page can help answer someone's question without receiving the visit. Being discovered, being cited and being read on the original site are no longer interchangeable outcomes. That distinction matters to a small newsroom, an independent documentation project or a community publication that needs readers, contributors or subscriptions, not merely a mention in an AI response.

There is at least something practical to measure. Google's generative AI reports in Search Console provide a dedicated view of visibility in AI search features. They do not replace the need to examine clicks, engagement and the actions visitors take after arriving. Nor does the change require a new set of secret SEO techniques: Google's guidance still points site owners towards crawlable pages, clear internal links and helpful, accessible content.

For Drupal and the wider open-source web, this is about more than search rankings. Community sites, maintainers and independent publishers make information freely available because people need it. AI search may help more people encounter that knowledge, but who will keep producing and maintaining it if the visits that sustain those sites become harder to earn? That is the question worth carrying into the next round of Search changes.

Follow The DropTimes on LinkedIn and Bluesky, or join #thedroptimes on Drupal Slack.

Kazima Abbas wrote and curated this issue of Editor’s Pick.

Gábor Hojtsy: Upgrade Status 5: triple the kinds of deprecations found, faster analysis and reporting, redesigned summaries for humans and LLMs

Upgrade Status 5: triple the kinds of deprecations found, faster analysis and reporting, redesigned summaries for humans and LLMs

This is a very long post, but trust me, it is worth it!

Upgrade Status is a Drupal module I maintain and is the centerpiece of getting a Drupal site ready for the next major version of Drupal core. It is currently used by more than 70,000 sites, and I hope this new version makes the work on all those sites significantly easier!

Gábor Hojtsy Mon, 11/16/2026 - 13:31

Security public service announcements: Upcoming critical Drupal core releases on November 18, 2026 - PSA-2026-11-16

Date: 2026-November-15Security risk: Critical 18 ∕ 25 AC:Complex/A:None/CI:All/II:All/E:Proof/TD:UncommonDescription: 

There will be a Drupal core security release for all supported branches on November 18, 2026 between 17:00 and 21:00 UTC. (To see this in your local timezone, refer to the Drupal Core Calendar.)

The Drupal Security Team urges you to reserve time for core updates at that time because exploits might be developed within hours or days.

The vulnerabilities are currently rated as critical and at least one can be exploited by anonymous users. More than one configuration is affected, so do not assume your site is safe.

We also recommend updating to the latest supported patch (bugfix) release for your site's version of Drupal before November 18, so that you can address any other upgrade issues before the security window.

Drupal Steward information

This issue is being mitigated by Drupal Steward. Sites that use Drupal Steward are already protected from known attack vectors. Other security advisories may be released on the same date without Drupal Steward mitigation. Sites should upgrade in the near future to ensure that they are protected from all published advisories.

Affected versions

All currently supported versions of Drupal core are affected, including:

  • Drupal 11.4.x
  • Drupal 11.3.x
  • Drupal 10.6.x

Drupal 12.0.0-beta3 and 11.5.0-beta1 are also affected. New beta or release candidate versions will be provided following the security updates for the currently supported branches.

All versions of Drupal prior to 10.6.x as well as all versions of Drupal 11 prior to 11.3.x are end-of-life and no longer supported. Sites on those versions should apply the interim mitigation steps that will be provided in the upcoming security advisory, and update as soon as possible to avoid this and other publicly disclosed vulnerabilities.

Disclosure policy

Neither the Security Team nor any other party is able to release any more information about this vulnerability until the announcement is made. Security release announcements will appear on the Drupal.org security advisory page, which has RSS feeds. The announcement will also be made public on:

If you have received an unsolicited email describing a potential Drupal core security issue, please do not forward it or act on instructions in it.

Coordinated By: 

Pages