On this page (8 sections)

Ubuntu has published security notice USN-9057-1 about rkhunter, the Linux rootkit scanner. According to the notice, rkhunter downloaded mirror updates over an insecure channel, and a remote attacker could possibly use this to execute arbitrary code.

If you run Ubuntu servers and use rkhunter to check them, this is worth a few minutes. The notice, as available to us, is short, so this article separates what is confirmed from what is not yet known.

What the notice says

The only detail we have from the primary source is one sentence: Ubuntu reports that rkhunter downloaded mirror updates over an insecure channel, and that a remote attacker could possibly use the issue to execute arbitrary code. The notice was dated 2026-11-11.

Only one publisher covers this story so far, and it is the distribution vendor itself. We have no independent analysis, and no reports of attacks in the wild.

What is not confirmed

The material we have does not include several details you would normally want. Treat each of these as unknown until you read the full notice:

  • No CVE identifier or CVSS score is given, so severity is unrated here.
  • Affected and fixed package versions, and which Ubuntu releases are covered, are not stated in the text we have.
  • The exact mechanism is not described, for example whether the insecure channel is plain HTTP, and what an attacker would need to position themselves to do.
  • There is no statement on whether the flaw has been exploited.

Check the full notice for the release table and fixed versions before you act on any version number.

Why insecure update channels matter

A rootkit scanner is a trusted tool that often runs as root, usually on a schedule. rkhunter can refresh some of its data files from mirrors. If that download is not protected by TLS or by a cryptographic signature check, anyone who can tamper with the traffic between the server and the mirror could substitute their own content.

What happens next depends on how the downloaded data is used. Ubuntu's wording, "possibly" executing arbitrary code, suggests the tampered content could end up being processed in a harmful way. This is a general explanation of the weakness class, not a description of the specific bug, which the notice does not detail.

The practical risk is highest for servers on untrusted networks or paths where traffic could be intercepted or redirected. A server in a well-controlled network is harder to attack this way, but you should still patch.

Who is realistically exposed

  • Ubuntu servers and workstations with the rkhunter package installed.
  • Systems where rkhunter runs automatically, for example from cron or a package-provided job, and is allowed to fetch updates.
  • Hosting administrators and agencies who add rkhunter to many client servers as a standard hardening step.

If rkhunter is not installed, this notice does not apply to that machine.

How to check your exposure

This read-only command shows whether rkhunter is installed and which version you have (Debian/Ubuntu). If it prints nothing or says not installed, you are not affected.

Check whether rkhunter is installed and its version (Debian/Ubuntu)Shell
dpkg -l rkhunter

This command shows the installed and candidate versions from your configured repositories. Compare the result with the fixed version listed in the Ubuntu notice for your release.

Show installed and available rkhunter versions (Debian/Ubuntu)Shell
apt-cache policy rkhunter

What to do now

  1. Find every Ubuntu host where rkhunter is installed, using the dpkg check above.
  2. Read USN-9057-1 and note the fixed version for each Ubuntu release you run.
  3. Refresh package lists and upgrade rkhunter through your normal update process.
  4. Until patched, avoid running rkhunter update tasks on untrusted networks.
  5. After updating, run your usual rkhunter check and review the output for anything unexpected.
  6. Record which hosts were updated, and when, so you can show the notice was handled.

This command refreshes package lists and upgrades only the rkhunter package (Debian/Ubuntu). Run it as root or with sudo, then re-run the version check to confirm the change.

Upgrade only rkhunter (Debian/Ubuntu)Shell
sudo apt update && sudo apt install --only-upgrade rkhunter
Tip. If you manage many servers, use your existing patch tooling rather than logging in one by one, and compare the result against the fixed version in the notice.

Detection and monitoring afterwards

Because the notice does not say whether attacks have happened, do a sanity review on servers that ran rkhunter updates over untrusted networks. Look at recent changes to rkhunter data files, unexpected processes, and new cron jobs or user accounts. Our guide on checking whether a website is hacked covers the web-facing side, and what to do if a site is hacked lists next steps if you find something.

Subscribe to Ubuntu security notices for the releases you run, so that follow-ups to USN-9057-1, such as a CVE assignment or a severity rating, reach you early. For the websites on those servers, an outside-in view helps too: Webforta Monitor tracks certificate, DNS and header changes, and the free malware scanner gives a quick check of a public site. These do not see inside the server, so they complement patching rather than replace it.

Timeline

Known dates
DateEvent
2026-11-11Ubuntu publishes USN-9057-1 on rkhunter
2026-11-12This article written; no CVE, severity score or exploitation report in the available research
This article will be only as complete as the notice behind it. If Ubuntu adds a CVE, severity or version details, rely on the vendor page over this summary.

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. USN-9057-1: rkhunter vulnerabilityubuntu.com ·
  • Ubuntu
  • rkhunter
  • USN
  • Linux security
  • supply chain