Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 16 Feb 2026.
Debian LinuxOperating system · Debian

CVE-2026-24061

CRITICAL · 9.8 CVSS v3.1 Published 2026-01-21
Fix available
A fix is available. Upgrade to after 2.7 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Public exploit Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
telnetd in GNU Inetutils through 2.7 allows remote authentication bypass via a "-f root" value for the USER environment variable.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The telnetd server in GNU Inetutils versions up to 2.7 contains an authentication bypass vulnerability where the USER environment variable is improperly processed. An attacker can set USER to '-f root' to bypass authentication and gain unauthorized root access to the system.

MitigationDisable the telnetd service immediately and migrate to SSH for remote access; if telnet is required, upgrade to a patched version of GNU Inetutils once available or apply a source code fix to reject the '-f' flag in USER.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Debian LinuxOperating system
Affected:= 11.0
InetutilsApplication
Affected:>= 1.9.3, <= 2.7

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed GNU Inetutils version
    Run 'inetutils --version' or 'dpkg -l | grep inetutils' on Debian systems, or 'rpm -qa | grep inetutils' on RHEL-based systems
    Affected if version is >= 1.9.3 and <= 2.7
  2. Verify telnetd server package is installed
    Run 'which telnetd' or check package manager for inetutils-telnetd package
    Affected if telnetd binary exists on the system
  3. Check if telnet service is enabled
    Run 'systemctl status telnet' or check /etc/inetd.conf for telnet entries, or check if port 23 is listening with 'netstat -tlnp | grep :23' or 'ss -tlnp | grep :23'
    Affected if telnet daemon or service is running or enabled
  4. Check telnetd is accessible remotely
    Attempt a telnet connection to the target on port 23, or verify the firewall allows inbound telnet traffic
    Affected if telnet port 23 is open and reachable from network

User is affected if GNU Inetutils version is between 1.9.3 and 2.7 AND telnetd service is installed and running, allowing remote network access to the telnet service.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 2.7
Vendor patch codeberg.org →
Interim mitigation

Disable the telnetd service immediately and migrate to SSH for remote access; if telnet is required, upgrade to a patched version of GNU Inetutils once available or apply a source code fix to reject the '-f' flag in USER.

Recommended fix Moderate confidence

GNU Inetutils version greater than 2.7 (or latest available package in Debian 11.0 updates)

  1. 1. Identify the telnetd service in your environment and determine if it is actively used.
  2. 2. If telnetd is not required, disable or remove it to eliminate the attack surface.
  3. 3. If telnetd is required, upgrade GNU Inetutils to a version newer than 2.7.
  4. 4. On Debian 11.0 systems, run 'apt update && apt install inetutils' to get the latest available package.
  5. 5. After upgrading, restart the telnetd service if it is running.
  6. 6. Verify the fix by checking the inetutils version with 'telnetd --version'.
Caveat Upgrading inetutils may introduce changes to other utilities (ftp, telnet, etc.); test in non-production environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Debian Linux Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-24061 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-24061 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data