Tag: Server Hardening

  • Drupal Security Update: Patch the Installer RCE (CVE-2026-132165) Now

    Drupal Security Update: Patch the Installer RCE (CVE-2026-132165) Now

    Drupal security update graphic: blue shield over a blocked installer path for CVE-2026-132165

    Introduction

    A Drupal security update released on November 18, 2026 fixes CVE-2026-132165, a highly critical remote code execution flaw in Drupal core’s installer (install.php). The Drupal Security Team has since updated its advisory to say it received a report of exploitation on live sites. If you run Drupal 10 or 11, update to 10.6.22, 11.3.22 or 11.4.13 and block the installer today.

    This guide summarizes the official advisories SA-CORE-2026-017 and SA-CORE-2026-018. It shows how to check your version, how to patch, and what to do if you cannot patch right away. It contains no exploit details.

    Key Facts: Drupal Security Update at a Glance

    • What: Drupal core 10.6.22, 11.3.22 and 11.4.13 (November 18, 2026) fix SA-CORE-2026-017 and SA-CORE-2026-018.
    • Main flaw: CVE-2026-132165. Under specific conditions, an attacker can use install.php to try to reinstall Drupal. This can lead to site takeover or remote code execution.
    • Second flaw: CVE-2026-132166, a “gadget chain” that is not directly exploitable on its own.
    • Affected: Drupal core before 10.6.22, 11.0.0 to before 11.3.22, and 11.4.0 to before 11.4.13. End-of-life branches get no fix.
    • Severity: “Highly critical” (20/25) on Drupal’s own risk scale. NVD and CVE.org had not published the CVE records yet when we checked.
    • Exploitation: the Drupal Security Team says it received a report of exploitation on live sites as early as November 19, 2026, 19:00 UTC (21:00 Kyiv time). The CVE is not in the CISA KEV catalog (version 2026.11.20).
    • Action: update Drupal core, block /core/install.php, and make sure the web server cannot write to settings.php.

    What Is CVE-2026-132165?

    CVE-2026-132165 is a flaw in Drupal’s web installer that can let an attacker reinstall a site and take it over.

    Drupal core ships with core/install.php, which you need only once, to set up a site. According to SA-CORE-2026-017, under specific conditions an attacker can use this installer to attempt to reinstall Drupal. The advisory says this can lead to site takeover or remote code execution. It also says some exploit paths are blocked if the web server cannot write to, or change permissions on, settings.php.

    Drupal’s advisory credits Anthropic’s OSS Scanner with the discovery. The risk string is AC:Complex/A:None/CI:All/II:All/E:Exploit/TD:Uncommon. In plain terms: no login is needed, the attack is complex, the impact on data is total, an exploit exists, and only an uncommon set of sites is exposed at a given time.

    What does SA-CORE-2026-018 fix?

    SA-CORE-2026-018 (CVE-2026-132166, “Moderately critical”, 14/25) removes a chain of methods in core that an attacker could abuse only if a separate insecure deserialization bug exists. Drupal says it is not directly exploitable. The same releases fix both issues.

    Which Drupal Versions Are Affected?

    All supported Drupal 10 and 11 branches before the November 18 releases are affected, and end-of-life branches will not get a patch.

    Drupal branchAffectedFixed inStatus
    11.4.x11.4.0 to 11.4.1211.4.13Supported until April 2027
    11.3.x11.3.0 to 11.3.2111.3.22Supported until Drupal 11.5.0 (December 2026)
    11.0.x to 11.2.xAllNo fixEnd-of-life
    10.6.xBefore 10.6.2210.6.22Supported until Drupal 11.5.0 (December 2026)
    10.5.x and older, Drupal 8 and 9AllNo fixEnd-of-life

    Drupal’s release history lists 11.4.13, 10.6.22 and 11.3.22 as published on November 18, 2026, between 16:52 and 17:30 UTC. Drupal 11.5 and 12.0 betas are not covered by security advisories.

    What Is the Security Impact?

    The worst case is full site takeover, including code execution on the server, without a login.

    A successful reinstall gives the attacker control of the site, which the advisory calls a site takeover. With that control, an attacker could run code, steal data, deface pages or host malware. The advisory rates the target distribution as “uncommon,” so not every site is exposed at every moment. Still, the exploitation report makes this Drupal security update a “patch now” task for every public Drupal site.

    Drupal Steward customers are already protected from known attack vectors, according to the advisory. Drupal still asks them to upgrade soon, in case new attack vectors appear.

    How Do I Check Whether My Drupal Site Is Affected?

    Check your exact Drupal core version, then test whether the installer is reachable from the internet.

    How do I check my Drupal version?

    In the admin UI, open Reports > Status report (/admin/reports/status). From the command line, use Composer or Drush in your project directory:

    composer show drupal/core | grep versions
    drush status --field=drupal-version

    Compare the result with the table above. Anything below 10.6.22, 11.3.22 or 11.4.13 needs the Drupal security update.

    How do I check whether install.php is exposed?

    Drupal’s documentation on securing the installer gives three test requests. Replace example.com with your domain:

    curl -I https://example.com/core/install.php
    curl -IL https://example.com/install.php
    curl -I https://example.com/core/install.php/foo

    All three should end in a 403 or 404 response. A 200 means the installer is reachable.

    How Do I Apply the Drupal Security Update?

    Update Drupal core to the fixed release for your branch, run database updates, then block the installer.

    1. Back up first. Back up the database and files so you can roll back.
    2. Update core with Composer. Drupal’s update guide uses composer update "drupal/core-*" --with-all-dependencies for sites based on drupal/core-recommended.
    3. Run database updates and clear caches: drush updatedb, then drush cache:rebuild.
    4. Check the Status report again and confirm the new version.
    5. Update every copy. Include staging, disaster-recovery copies and container images.
    Drupal security update remediation flow: check version, update core, block install.php, verify 403 or 404, lock settings.php
    How to apply the Drupal security update: patch core, block install.php, verify, then lock settings.php.

    How do I block install.php after installation?

    Drupal recommends blocking the installer in the web server configuration. For Apache, add this to the virtual host (not to .htaccess, which causes a 500 error for this block):

    <Location "/core/install.php">
      Require all denied
    </Location>

    For Nginx, add this inside the HTTPS server block, then run nginx -t before reloading:

    location ^~ /core/install.php {
      return 404;
    }

    Drupal warns against an exact match (location = /core/install.php), because some setups would miss /core/install.php/foo. On shared hosting, a <Files "install.php"> rule in .htaccess works, but Composer can overwrite .htaccess. Do not block update.php by mistake.

    What if I cannot update right away?

    Block the installer now, as SA-CORE-2026-017 advises, and schedule the Drupal security update for the next possible window. Also make sure the web server user cannot write to settings.php or change its permissions. This blocks some exploit paths, but it is not a full fix. Sites on end-of-life branches should block the installer and plan an upgrade to a supported branch.

    Are there known issues with the new releases?

    Yes. The 10.6.22 release notes list a theme registry regression (“Theme hook field not found”) that affects some contributed and custom code, including Search API. Drupal says the fix will ship in 11.4.14. Do not skip the Drupal security update because of it. Test on staging first.

    Additional Security Recommendations

    A Drupal security update closes this flaw, but these habits reduce the damage from the next one:

    FAQ

    Is CVE-2026-132165 being exploited?

    Yes, according to Drupal. The Security Team updated SA-CORE-2026-017 to say it received a report of exploitation on live sites as early as November 19, 2026, 19:00 UTC. As of November 21, 2026, the CVE is not in CISA’s KEV catalog (version 2026.11.20).

    Which Drupal security update do I need?

    Install 11.4.13 on Drupal 11.4, 11.3.22 on Drupal 11.3, or 10.6.22 on Drupal 10.6. Older branches are end-of-life and need an upgrade to a supported branch.

    Does blocking install.php fix the vulnerability?

    It removes the entry point that SA-CORE-2026-017 describes, and Drupal recommends it as the stopgap. It is not a replacement for updating core, which also fixes CVE-2026-132166.

    Is Drupal 7 affected?

    The advisory lists affected versions only for Drupal 10 and 11 and says Drupal 8 and 9 are end-of-life. It does not mention Drupal 7, so check with your Drupal 7 extended support vendor.

    Do I need to do anything on managed Drupal hosting?

    Confirm with your host that core is at a fixed version and that /core/install.php returns 403 or 404. Some managed platforms already block the installer, but test it yourself with the curl commands above.

    Conclusion

    This Drupal security update fixes an installer flaw that Drupal says attackers are already using. Update to 10.6.22, 11.3.22 or 11.4.13, block /core/install.php, lock down settings.php, and check every site you manage today.

    References

    All links below returned HTTP 200 when checked on November 21, 2026.

    Related Articles

    Last Verified: November 21, 2026. Prepared by SafeWebAcademy from the official Drupal security advisories, release notes and documentation linked above, and the CISA KEV catalog. This is not an official Drupal Association publication. Security details can change, so check the linked advisories for updates.

  • How to Secure Your Ubuntu Server: A Beginner-Friendly Guide

    How to Secure Your Ubuntu Server: A Beginner-Friendly Guide

    Ubuntu server secured with firewall and SSH keys

    Setting up an Ubuntu server is an exciting step, whether you’re hosting a website, running applications, or managing a Linux server for your business. But here’s the thing: without proper security measures, your server could be a sitting duck for cyberattacks. In this guide, we’ll walk you through some essential tools and techniques to secure your Ubuntu server, including enabling SSH, configuring firewalls, and using tools like Fail2ban. Let’s dive in!


    Why Securing Your Ubuntu Server Matters

    Imagine this: you’ve just set up your shiny new Linux server hosting environment, and everything is running smoothly. But without security, your server is vulnerable to attacks that could steal sensitive data, disrupt services, or even install malware. Yikes, right? That’s why securing your Ubuntu server setup is non-negotiable.


    1. Fail2ban: Your First Line of Defense

    Fail2ban is like a bouncer for your server. It monitors login attempts and bans IP addresses that fail to authenticate after a certain number of tries. For example, if someone tries to SSH into your server without the correct key or password, Fail2ban steps in and blocks them.

    How to Install Fail2ban on Ubuntu Server

    1. Update your package list:sudo apt update
    2. Install Fail2ban:sudo apt-get install fail2ban

    Configuring Fail2ban

    The default configuration file is located at /etc/fail2ban/jail.conf. To customize it:

    1. Back up the default file:sudo cp /etc/fail2ban/jail.conf /etc/fail2ban/jail.local
    2. Open the configuration file:sudo nano /etc/fail2ban/jail.local
    3. Adjust these key parameters:
      • ignoreip: Whitelist trusted IPs (e.g., your home IP).
      • bantime: Set how long an IP should be banned (in seconds).
      • findtime: Define the time window for counting failed logins.
      • maxretry: Set the number of failed attempts before banning.

    For example, to whitelist your home IP and ban attackers for 10 minutes:

    ignoreip = 192.168.1.1
    bantime = 600
    maxretry = 5
    

    2. UFW: Simplifying Firewall Management

    UFW (Uncomplicated Firewall) is a user-friendly tool to manage your Ubuntu server’s firewall. It helps you control incoming and outgoing traffic, ensuring only authorized connections get through.

    How to Install and Enable UFW

    1. Check if UFW is already installed:sudo ufw status
    2. If not, install it:sudo apt update sudo apt install ufw

    Configuring UFW for SSH and More

    By default, UFW blocks all incoming traffic. To allow SSH access:

    sudo ufw allow ssh
    

    Want to open another port? For example, if you’re hosting a web server on port 8080:

    sudo ufw allow 8080
    

    Enable UFW to start protecting your server:

    sudo ufw enable
    

    To view your rules:

    sudo ufw status numbered
    

    Pro Tip: Always test your setup after enabling UFW to ensure you haven’t accidentally blocked necessary traffic.


    3. SSH Key Authentication: Ditch Passwords for Good

    Passwords are so last decade. SSH key authentication is a more secure way to log into your Ubuntu server. It uses a pair of cryptographic keys (public and private) to verify your identity.

    How to Enable SSH on Ubuntu Server

    1. Check if SSH is installed:sudo systemctl status ssh
    2. If it’s not running, start it:sudo systemctl start ssh
    3. If SSH isn’t installed, add it:sudo apt-get install openssh-server

    Setting Up SSH Key Authentication

    1. Generate an SSH key pair on your local machine:ssh-keygen -t rsa -b 4096 Press “Enter” to save the key in the default location (~/.ssh/id_rsa) and set a passphrase for extra security.
    2. Copy your public key to the server:ssh-copy-id username@<server_ip>
    3. Disable password authentication for added security:
      Open the SSH configuration file:sudo nano /etc/ssh/sshd_config Find the line PasswordAuthentication and set it to no.
    4. Restart the SSH service:sudo systemctl restart ssh

    Now, try logging in:

    ssh username@<server_ip>
    

    If it works, congrats! You’ve just leveled up your server security.

    4. Don’t Forget Backups: Your Safety Net

    Even with the best security tools in place, things can still go wrong—whether it’s hardware failure, accidental deletions, or a successful cyberattack. That’s why having a solid backup strategy is just as important as setting up firewalls or SSH keys. Backups act as your safety net, ensuring you can quickly restore your system and data if disaster strikes.

    Want to learn how to set up reliable backups for your Ubuntu server? Check out our detailed guide here: How to Back Up Your Ubuntu Server.

    Pro Tip: Automate your backups so you never have to remember to run them manually. Regular, automated backups will save you countless headaches down the road.


    FAQs About Ubuntu Server Security

    Q: Can I use Fail2ban and UFW together?
    Absolutely! They complement each other. Fail2ban handles brute-force attacks, while UFW manages overall traffic rules.

    Q: What happens if I lose my SSH private key?
    If you lose your private key, you won’t be able to log in. Always keep a backup of your private key in a secure location.

    Q: Is SSH key authentication mandatory?
    No, but it’s highly recommended. Passwords are easier to crack, while SSH keys provide a stronger layer of security.


    Wrapping Up

    Securing your Ubuntu server doesn’t have to be overwhelming. By using tools like Fail2ban, UFW, and SSH key authentication, you can protect your Linux server hosting environment from common threats. Whether you’re setting up a personal project or managing a business-critical application, these steps will give you peace of mind.

    Related reading