CVE-2022-26110

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.

Published: 2022-04-06 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2022-26110 is rated Moderate Risk (56.9/100): CVSS High severity, with medium exploitation likelihood (EPSS 0.45%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2022-26110

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2025-11-21 0.74% 0.45% -0.29%
2 2025-11-18 0.45% 0.74% +0.29%
3 2025-10-15 — 0.45% —

Full EPSS history (9 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2022-26110

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.8 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.8 5.9 [email protected]
6.5 2.0 MEDIUM
AV:N/AC:L/Au:S/C:P/I:P/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:S)
A single authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:P)
Partial availability impact.
 8.0 6.4 [email protected]

Weakness enumeration for CVE-2022-26110

OS Trackers for CVE-2022-26110

vendor priority summary link
debian not yet assigned CVE-2022-26110 not yet assigned priority: Debian including 1 source packages (condor), 3 status rows across 3 suites (forky, sid, trixie): resolved 3. https://security-tracker.debian.org/tracker/CVE-2022-26110
ubuntu low CVE-2022-26110 low priority: Ubuntu including 1 source packages (condor), 9 status rows across 9 suites (bionic, focal, noble, oracular, plucky, questing, trusty, upstream, xenial): needs-triage 7, ignored 2. https://ubuntu.com/security/CVE-2022-26110

Affected software / configurations for CVE-2022-26110

Vendor Product Version Raw CPE
wisc htcondor >= 8.8.0, < 8.8.16 cpe:2.3:a:wisc:htcondor:*:*:*:*:*:*:*:*
wisc htcondor >= 9.0.0, < 9.0.10 cpe:2.3:a:wisc:htcondor:*:*:*:*:*:*:*:*
wisc htcondor >= 9.1.0, < 9.6.0 cpe:2.3:a:wisc:htcondor:*:*:*:*:*:*:*:*
debian debian_linux 9.0 cpe:2.3:o:debian:debian_linux:9.0:*:*:*:*:*:*:*
debian debian_linux 10.0 cpe:2.3:o:debian:debian_linux:10.0:*:*:*:*:*:*:*

References for CVE-2022-26110

cvelogic Threat Intelligence