Tag: Ubuntu

  • Apache HTTP Server 2.4.71: Patch mod_http2 CVE-2026-119618

    Apache HTTP Server 2.4.71: Patch mod_http2 CVE-2026-119618

    Apache HTTP Server 2.4.71 security update graphic: orange shield with a keyhole and the mod_http2 fix CVE-2026-119618

    Introduction

    Apache HTTP Server 2.4.71, released on November 11, 2026, fixes three vulnerabilities, including CVE-2026-119618, a critical flaw in mod_http2 that the Apache project says can lead to remote code execution. Apache httpd still powers many WordPress, PHP and shared hosting servers, and HTTP/2 is common on modern sites. If you run Apache 2.4.55 or later with HTTP/2, plan the update now.

    This article summarizes the official Apache advisory and Linux distribution notices, shows how to check your server, and explains how to update. It contains no exploit details.

    Key Facts: Apache HTTP Server 2.4.71 at a Glance

    • What: Apache HTTP Server 2.4.71 (November 11, 2026) fixes CVE-2026-119618, CVE-2026-106023 and CVE-2026-109163.
    • Most serious: CVE-2026-119618, a race condition in mod_http2 (assign_headers()) that can lead to remote code execution. The Apache project rates it critical.
    • Affected: Apache httpd 2.4.55 to 2.4.70 with mod_http2, and standalone mod_h2 2.0.8 to 2.0.42. Distribution packages with older version numbers can also be affected.
    • Severity: critical (Apache project). CVSS v3.1 8.1 from CISA’s enrichment in NVD; Ubuntu rates it “High” priority.
    • Exploitation: none reported. CISA’s SSVC entry lists exploitation as “none,” and the CVE is not in the CISA KEV catalog (version 2026.11.18).
    • Action: upgrade to 2.4.71 or your distribution’s patched package, then restart Apache.

    What Does Apache HTTP Server 2.4.71 Fix?

    Apache HTTP Server 2.4.71 fixes one critical, one important and one low-severity issue, according to the Apache httpd security page.

    CVEModuleIssueApache severityCVSS v3.1 (CISA ADP)
    CVE-2026-119618mod_http2Race condition in assign_headers(), heap corruption and possible remote code executionCritical8.1
    CVE-2026-106023mod_mdNULL pointer dereference that crashes a child processImportant7.5
    CVE-2026-109163mod_vhost_aliasOne-byte stack buffer overwrite (after CVE-2026-63292)Low5.9

    The Apache project does not publish CVSS scores. The scores above come from CISA’s Authorized Data Publisher entries in NVD. NVD itself had not finished analyzing CVE-2026-106023 and CVE-2026-109163 when we checked.

    Which Apache Versions Are Affected?

    Upstream Apache httpd 2.4.70 and earlier are affected, but the exact range depends on the CVE and on how your distribution packages mod_http2.

    CVEAffected (Apache project)Fixed in
    CVE-2026-1196182.4.55 to 2.4.70; mod_h2 2.0.8 to 2.0.422.4.71
    CVE-2026-1060232.4.30 to 2.4.702.4.71
    CVE-2026-1091632.4.69 to 2.4.702.4.71

    NVD’s descriptions give slightly narrower ranges for the two lower-severity CVEs (ending at 2.4.69). We follow the Apache project’s page.

    Why can older distribution versions be affected?

    Distributions often backport newer mod_http2 code into older httpd packages. Ubuntu’s security notes say exactly this for CVE-2026-119618, and Ubuntu lists its 22.04 package (based on 2.4.52) as affected and fixed. So check your vendor’s tracker, not just the upstream version number.

    DistributionFixed package (CVE-2026-119618)
    Ubuntu 26.04 LTS2.4.66-2ubuntu2.8
    Ubuntu 24.04 LTS2.4.58-1ubuntu8.19
    Ubuntu 22.04 LTS2.4.52-1ubuntu4.27
    Ubuntu 20.04 LTS2.4.41-4ubuntu3.23+esm11 (Ubuntu Pro)
    Debian 13 (trixie)2.4.71-1~deb13u1 (DSA-6620-1)
    Debian 12 (bookworm)2.4.71-1~deb12u1 (DLA-4902-1)

    Ubuntu lists 18.04 and older as not affected. For Red Hat, AlmaLinux and other platforms, check the vendor pages linked from the NVD record.

    What Is the Security Impact?

    The worst case is remote code execution through mod_http2, while the other two issues mainly crash Apache child processes.

    What can CVE-2026-119618 do?

    The Apache advisory describes a concurrency bug: shared resources are used without proper synchronization in mod_http2’s assign_headers() function. This can corrupt heap memory and, according to the advisory, lead to remote code execution. CISA’s vector marks it as network-reachable without authentication but with high attack complexity. That fits a race condition, which is hard but not impossible to win.

    What about mod_md and mod_vhost_alias?

    CVE-2026-106023 lets a request crash an Apache child process when mod_md, Apache’s built-in ACME certificate module, is in use. CVE-2026-109163 is a one-byte stack overwrite in mod_vhost_alias that affects only 2.4.69 and 2.4.70. Ubuntu’s notice says it could possibly lead to code execution.

    How Do I Check Whether Apache HTTP Server 2.4.71 Is Needed?

    Check the installed version and package release, then confirm whether mod_http2 is loaded and HTTP/2 is enabled.

    How do I check my Apache version?

    apache2 -v          # Debian/Ubuntu
    httpd -v            # RHEL/AlmaLinux/Fedora
    dpkg -l apache2     # full Debian/Ubuntu package version
    rpm -q httpd        # full RPM package version

    Compare the full package version with the table above or your vendor’s tracker. On managed or shared hosting, ask your provider whether USN-9090-1, DSA-6620-1 or an equivalent fix is installed.

    How do I check whether HTTP/2 is enabled?

    apache2ctl -M 2>/dev/null | grep -E "http2|md_module|vhost_alias"
    grep -rniE "^\s*Protocols" /etc/apache2 /etc/httpd 2>/dev/null

    If http2_module is loaded and a Protocols line includes h2 or h2c, treat CVE-2026-119618 as urgent.

    How Do I Fix These Apache Vulnerabilities?

    Install Apache HTTP Server 2.4.71 or your distribution’s patched package, then restart Apache.

    1. Back up first. Copy your Apache configuration and, for WordPress, follow our guide on how to back up WordPress.
    2. Update the package. On Ubuntu and Debian run sudo apt update && sudo apt install --only-upgrade apache2. On RPM-based systems use sudo dnf upgrade httpd.
    3. Check and restart. Run apachectl configtest, then restart Apache so all child processes use the fixed code.
    4. Check standalone mod_h2. The advisory lists mod_h2 2.0.8 to 2.0.42 as affected; check the mod_h2 project for a fixed release.
    5. Rebuild containers based on httpd or distribution images.

    What if I cannot update right away?

    The Apache advisory does not list a workaround, so the update is the fix. If your site does not need HTTP/2, removing h2 and h2c from Protocols takes mod_http2 out of the request path. This is our assessment, not vendor guidance, and it does not address CVE-2026-106023 or CVE-2026-109163.

    Additional Security Recommendations

    Applying Apache HTTP Server 2.4.71 is the main defense. These habits limit the damage from the next web server bug:

    FAQ

    Is CVE-2026-119618 being exploited?

    No exploitation has been reported as of November 20, 2026. CISA’s SSVC entry lists exploitation as “none,” and the CVE is not in the KEV catalog (version 2026.11.18). Public exploit availability is unknown.

    Am I affected if I run Apache 2.4.52 on Ubuntu 22.04?

    Yes, unless you have package 2.4.52-1ubuntu4.27 or later. Ubuntu backported newer mod_http2 code, so its 2.4.52 package is affected even though upstream 2.4.52 is older than 2.4.55.

    Do I need Apache HTTP Server 2.4.71 if HTTP/2 is disabled?

    Yes, still update. CVE-2026-119618 needs mod_http2, but the mod_md and mod_vhost_alias fixes also matter, and a later configuration change could enable HTTP/2.

    Is nginx affected by these CVEs?

    No. These CVEs are specific to Apache httpd modules. Nginx had its own security release on November 18, 2026.

    Conclusion

    Apache HTTP Server 2.4.71 closes a critical mod_http2 race condition and two smaller bugs. Check your package version against your vendor’s tracker, install Apache HTTP Server 2.4.71 or the patched package, and restart Apache today.

    References

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

    Related Articles

    Last Verified: November 20, 2026. Prepared by SafeWebAcademy from the official Apache HTTP Server advisory, NVD records and Linux distribution security notices linked above. This is not an official Apache Software Foundation 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