dbcve.org
Debian LinuxOperating system · Debian

CVE-2022-26110

HIGH · 8.8 CVSS v3.1 Published 2022-04-06
Fix available
A fix is available. Upgrade to 8.8.16 / 9.0.10 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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
An issue was discovered in HTCondor 8.8.x before 8.8.16, 9.0.x before 9.0.10, and 9.1.x before 9.6.0. When a user authenticates to an HTCondor daemon via the CLAIMTOBE method, the user can then impersonate any entity when issuing additional commands to that daemon.

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

HTCondor contains a flaw where the CLAIMTOBE authentication method allows any authenticated user to impersonate any other user or entity when sending subsequent commands to the daemon. This enables privilege escalation and unauthorized access to resources managed by HTCondor.

MitigationDisable or restrict the CLAIMTOBE authentication method in HTCondor daemon configurations, and upgrade to version 8.8.16, 9.0.10, or 9.6.0 or later which contain the fix.

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:= 9.0= 10.0
HtcondorApplication
Affected:>= 8.8.0, < 8.8.16>= 9.0.0, < 9.0.10>= 9.1.0, < 9.6.0

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 HTCondor daemon version
    Run `condor_version` command or check the installed package version (e.g., `dpkg -l | grep htcondor` on Debian or `rpm -q htcondor` on RHEL-based systems)
    Affected if The version is >= 8.8.0 and < 8.8.16, OR >= 9.0.0 and < 9.0.10, OR >= 9.1.0 and < 9.6.0, OR the package is from Debian 9.0 or 10.0
  2. Locate HTCondor configuration files
    Check for configuration in /etc/condor/condor_config, /etc/condor/config.d/, or the location pointed to by $CONDOR_CONFIG environment variable
    Affected if Configuration files exist and are readable
  3. Check if CLAIMTOBE authentication method is enabled
    Search configuration for CLAIMTOBE in AUTHENTICATION_METHODS, SEC_DEFAULT_AUTHENTICATION_METHODS, or similar authentication-related settings using `grep -r "CLAIMTOBE" /etc/condor/`
    Affected if CLAIMTOBE appears in any authentication method list (e.g., AUTHENTICATION_METHODS = CLAIMTOBE, ...) and is not commented out
  4. Verify the CLAIMTOBE method is actually used by HTCondor
    Run `condor_config_val SEC_DEFAULT_AUTHENTICATION_METHODS` to see the active runtime configuration for authentication methods
    Affected if CLAIMTOBE is listed among the active authentication methods and is not restricted to a specific identity list

You are affected if HTCondor version is within the vulnerable ranges AND the CLAIMTOBE authentication method is enabled in the active configuration.

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 8.8.16 / 9.0.10 / 9.6.0 or later
Fixed in 8.8.169.0.109.6.0
Interim mitigation

Disable or restrict the CLAIMTOBE authentication method in HTCondor daemon configurations, and upgrade to version 8.8.16, 9.0.10, or 9.6.0 or later which contain the fix.

Recommended fix High confidence

Upgrade to HTCondor 8.8.16, 9.0.10, or 9.6.0 (or later) depending on your current version branch

  1. Identify the currently installed HTCondor version using 'condor_version' or package manager
  2. For HTCondor 8.8.x users: Upgrade to version 8.8.16 or later, or migrate to the 9.x stable release
  3. For HTCondor 9.0.x users: Upgrade to version 9.0.10 or later
  4. For HTCondor 9.1.x through 9.5.x users: Upgrade to version 9.6.0 or later
  5. Verify the upgrade was successful by running 'condor_version'
  6. Restart HTCondor daemons to apply the changes using 'condor_restart' or system service manager
  7. For Debian systems: Run 'apt-get update && apt-get install htcondor' to install the fixed package
Caveat Standard upgrade considerations apply - review release notes for version-specific changes; HTCondor 8.8.x may be end-of-life, consider migrating to 9.x stable

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

Fix this in Debian Linux Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Get it on GitHub Scan in the browser

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-2022-26110 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