Talking Drupal #579 - Women in Drupal
Today we are talking about Woman, Drupal, and Woman in Drupal with guests Ashleigh Fox, Sinduri Guntupalli, and Rachel Lawson. We'll also cover Legal as our module of the week.
For show notes visit: https://www.talkingDrupal.com/579
EvolveDigital NYC 2026 Speakers Address CMS Decisions, Drupal Crawlers and AI
Recalls at Race Pace
On Wednesday 18 November two security releases landed within three hours: nginx 1.31.9 with ten fixes, four of them reachable on a BOA server, where every site speaks HTTP/2, HTTP/3 and TLS 1.3, and Drupal core's critical SA-CORE-2026-017, a remote code execution through the installer. Both carry the mark of this year, since Drupal's advisory credits a scanner from an AI lab and nginx's change log an AI security firm. On BOA, our open-source Ægir hosting stack for Drupal and Backdrop, the installer has answered 404 on every site since 2012, which we proved again with 84 requests, so site owners update core this week instead of this hour. For nginx the security floor built for PHP in October was extended the same evening, so a BOA server below 1.31.9 books an upgrade for itself inside thirty minutes, automatic updates off or not. Two and a half hours from the go to the stable trees, with AI doing the legwork and a human holding the keys, and why we think that is no longer optional. Giving an AI Agent Its Own Linux User (Without Breaking DDEV)
TL;DR: My coding agent runs on my WSL2 machine as its own Linux user, with its own home directory and its own rootless Docker daemon. DDEV runs as that same user, in my terminal and in the agent's. My workflow did not change. This post explains why I did it, what it took, and what broke along the way.
The surprise came quickly: My agent had a terminal open in a client project, about to run ddev composer install, and I wanted to know what it could reach if a task ever went sideways. The answer was: everything. The agent ran as my user, so it could read my SSH keys, push with my Git and gh credentials, reach everything on the Windows side through /mnt/c, and talk to a Docker daemon running as root. Its permission system asked before every Bash command, and I approved commands in five-second intervals, all day. At some point I stopped reading the prompts and clicked allow blindly. That was the moment I knew the agent and I needed a different kind of protection.
An agent with a shell can wreck the machine it runs on (delete files, fill the disk), take it over (steal credentials, plant a backdoor, use the Docker socket), write code that does more than the task asked, ship private code and secrets somewhere else, or reach network services it was never meant to touch. Wherever it runs, those risks travel with it.
SQL Sync for DDEV: Drush-Style Database Sync for Any SSH Server
Anyone who has worked with Drupal knows this command:
drush sql-sync @prod @self
One command, and the local site has a copy of the production database.
I use Drush a lot, so I wanted the same thing for my personal projects. They are Laravel, WordPress and plain PHP sites, and they live on all sorts of hosting: shared accounts, VPSs, dedicated boxes — a good number of them running cPanel, which itself runs on shared and dedicated hosting alike. What I had instead was the usual mix of phpMyAdmin exports and one-off scripts that I had to remember each time.
DDEV does have pull providers. The ready-made ones are for hosted platforms like Pantheon and Acquia, but the examples it ships also include an rsync one, for pulling a dump down from a plain server over SSH. I do not want to overstate the gap: that example works. But it is a starting point you adapt, not a finished tool. Every project needs its own provider file, written and kept up to date separately, and sanitize is on you. I kept missing the Drush shape: one aliases file, the same command in every project, and sanitize taken care of. So this add-on is that shape, packaged: ddev-sql-sync.
One thing to state up front: I designed this add-on, and it was built and tested with the help of an AI agent, Ryan (Muse), working under my direction. There is a bit more about that at the end.
Where I use it:
Drupal core - Moderately critical - Gadget chain - SA-CORE-2026-018
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().
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
Drupal core - Critical - Remote code execution - SA-CORE-2026-017
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.
The Work We Want: AI, Code Directors, and Collective Power
Drupal CRM integration for pre-qualified inquiries
An informed buyer shouldn’t have to repeat their research to sales. Drupal CRM integration can connect forms and agent endpoints to your CRM without losing intent, consent evidence, or inquiries during an outage. DrupalCamp Spain 2026 Speakers Examine AI Reliability and Human Agency
Association Website Design: Lessons From the 100 Largest US Associations
Contributor Training: Advanced coder.ddev.com Usage

coder.ddev.com gives you a DDEV environment in the cloud, with nothing installed on your own machine. Since the announcement it has grown a Drupal issue picker, a freeform template for any DDEV project, and several ways to run Claude Code inside a workspace.
Here's our November 11, 2026 Contributor Training on advanced coder.ddev.com usage:
The slides are available at rfay.github.io/advanced-coder-presentation, with source at github.com/rfay/advanced-coder-presentation.
What coder.ddev.com Iscoder.ddev.com is a free, experimental service built on the open source Coder project. Each workspace is an isolated Docker-in-Docker container (using Sysbox) with DDEV, Docker, Git, VS Code, and Claude Code already installed. The tools run on the server and use the workspace's files and configuration.
It is experimental. There are no guarantees about uptime or data retention, and a workspace that sits idle for 14 days is deleted, so keep your work in Git.
Is DDEV Affected by nginx2root?
Several of you have asked whether DDEV is affected by nginx2root, published today by Xint. The research chains five nginx memory-corruption bugs (CVE-2026-123007, CVE-2026-123634, CVE-2026-123633, CVE-2026-121810, and CVE-2026-113425) with an unpatched Linux kernel SCTP flaw. Each nginx bug gives an unauthenticated remote client code execution as the nginx worker, and the kernel bug then takes that worker to root on the host, including out of a Docker container.
The short answer is that normal DDEV use isn't at risk.
Why DDEV isn't exposedDDEV is normally used for local development, so it isn't reachable by an attacker of this type. If you use DDEV for internet-facing hosting, pay a little more attention, but the reasons below still apply.
The vulnerable nginx features aren't turned on by default. The five CVEs need HTTP/2 on a listener, HTTP/3/QUIC listeners, mirror combined with a resolver and a request-derived proxy_pass, or the mail proxy with auth_http. DDEV's nginx configurations use listen 443 ssl without http2, and use none of the others.
Traefik is in front of nginx. Your browser talks to ddev-router, which handles any HTTP/2 or HTTP/3 and forwards plain HTTP/1.1 to nginx in the web container. The web container's own ports are bound only to 127.0.0.1 unless you've turned on bind_all_interfaces.
The second stage is a kernel bug, and an attacker can only try it after getting code running inside the web container. In DDEV that container already runs your project's own code. On Linux hosts that don't need SCTP, you can block the module:
Inside the Pyramid: The Ideal Shape for Drupal’s Test Suite
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:
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.
Drupal AI Content Review Alpha Can Overwrite Entire Fields
How to make your Drupal content readable by AI Crawlers and LLMs with Markdown Mirror
Why Some Drupal 11 Module Fixes Have Yet to Reach Official Releases
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 gapDrupal 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.