Database/Control plane, storage & DevOps
HTCondor (IDToken authorization restrictions): The per-token authorization restrictions attached with
Impact
The per-token authorization restrictions attached with condor_token_create -authz are not enforced. A token you deliberately minted as read-only, or scoped to one operation, performs everything the underlying identity is entitled to. Sites that use restricted tokens to hand limited access to a partner or a CI system have a boundary that does not exist.
Who can reach it
Any holder of an IDToken that the target daemon can validate. The attacker does not need to be permitted by the daemon's configured authorization policy for the restriction bypass itself.
What to do
Upgrade to HTCondor 23.0.22, 23.10.22, 24.0.6 or 24.6.1 and restart the daemons. Then inventory every token issued with -authz, or approved via condor_token_request_approve, and reissue them - each one has been operating as an unrestricted token for its identity.
References
Related entries
- ConnectWise ScreenConnect: ViewState code injectionCVE-2025-3935 · ConnectWise ScreenConnectHigh
- Coder: prebuilds system-user session token survives workspace claim and stays validCVE-2025-58437 · Coder (prebuilt workspace session token lifecycle)High
- MinIO (service accounts / STS session policies): The session policy attached to a service account or STS credential isCVE-2025-62506 · MinIO (service accounts / STS session policies)High
- Apache CloudStack: MinIO policies survive bucket deletion, giving a former owner access to a new bucket of the same nameCVE-2025-66467 · Apache CloudStack (MinIO object store policy cleanup on bucket deletion)High
- ansible-core: ansible-galaxy role name path traversal writes files outside the roles directoryCVE-2026-105929 · ansible-core (ansible-galaxy role install)High
- Jenkins: symlinks in artifacts let a job configurer write files anywhere on the controller filesystemCVE-2026-117617 · Jenkins controller (artifact extraction, symlink TOCTOU)High
This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.