CVE-2026-24061
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 · uneditedtelnetd 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 confidenceThe 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.
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= 11.0>= 1.9.3, <= 2.7CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check installed GNU Inetutils versionRun 'inetutils --version' or 'dpkg -l | grep inetutils' on Debian systems, or 'rpm -qa | grep inetutils' on RHEL-based systemsAffected if version is >= 1.9.3 and <= 2.7
-
Verify telnetd server package is installedRun 'which telnetd' or check package manager for inetutils-telnetd packageAffected if telnetd binary exists on the system
-
Check if telnet service is enabledRun '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
-
Check telnetd is accessible remotelyAttempt a telnet connection to the target on port 23, or verify the firewall allows inbound telnet trafficAffected 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.
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 · scopedDisable 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.
GNU Inetutils version greater than 2.7 (or latest available package in Debian 11.0 updates)
- 1. Identify the telnetd service in your environment and determine if it is actively used.
- 2. If telnetd is not required, disable or remove it to eliminate the attack surface.
- 3. If telnetd is required, upgrade GNU Inetutils to a version newer than 2.7.
- 4. On Debian 11.0 systems, run 'apt update && apt install inetutils' to get the latest available package.
- 5. After upgrading, restart the telnetd service if it is running.
- 6. Verify the fix by checking the inetutils version with 'telnetd --version'.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-24061 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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