Skip to content
NewCybercrime Report 2026 · Eight Chapters · A Post Is Not An Incident → Explore The ChaptersCybercrime Report 2026 → Explore

Rucio SSH Challenge Token Flaw (CVE-2026-100397)

CVE-2026-100397 is an authentication bypass in Rucio that can let an unauthenticated requester impersonate an account, including an administrator.

Reviewed by
Brandefense Analyst Team
Published
Reading Time
2 min read
CVE ID
CVE-2026-100397
Vendor
Rucio
Affected Product
Rucio (pip package)
Exploitation
Not confirmed
Published
2026-08-11

Rucio's advisory says SSH challenge tokens are accepted as ordinary authentication credentials, although they should serve only as short-lived challenges.GitHub rates the issue 9.8 Critical under CVSS 3.1 and lists improper authentication (CWE-287) and authentication bypass (CWE-305). Its advisory does not provide a CVSS 4.0 score. Teams can use a vulnerability intelligence platform to track each affected Rucio deployment and its corrected release.

What it allows

How Does CVE-2026-100397 Bypass Rucio Authentication?

Rucio's advisory says the server stores SSH challenge tokens alongside ordinary authentication tokens. Its token validation function fails to distinguish the two token types. A requester can obtain a short-lived challenge for a chosen account without signing in, then present it as an authentication credential.

The advisory says that chosen account can be an administrator. Successful misuse would give requests the account's permissions during the challenge's ten-second lifetime. The short lifetime limits the window, but it does not correct the missing token-type check.

What Should Defenders Investigate?

Exploitation status is unknown. The available CISA KEV catalog snapshot, version 2026.11.10, predates the GitHub database update and does not list this CVE. That catalog fact cannot establish whether the flaw has been misused.

Review Rucio authentication records and administrative activity around affected services for unexplained account use. Correlate any suspicious activity with other available access records, and follow the incident response plan if an unauthorized session is suspected. These are investigative recommendations derived from the advisory's account-impersonation mechanism, not indicators of confirmed attacks.

Who is affected

Which Rucio Versions Are Affected?

The advisory lists the pip package rucio from 1.14.0.post1 up to, but excluding, 35.9.1. It separately lists 36.0.0rc1 to before 38.6.1, 39.0.0rc1 to before 40.4.2, and 41.0.0rc1 to before 41.1.1. These intervals include the stated release candidates.

The fixed versions are 35.9.1, 38.6.1, 40.4.2, and 41.1.1 for their respective lines. Inventory each Rucio service that issues or accepts authentication tokens, then compare its installed package version with the corresponding advisory interval. A patch management record should capture the running version after the upgrade.

Timeline

  1. 2026-08-11

    Rucio published the security advisory for this flaw.

  2. 2026-11-13

    The GitHub Advisory Database published and last updated its reviewed record.

What to do

  1. Inventory Rucio installations

    Identify Rucio services that issue or validate authentication tokens. Record the installed pip package version and compare it with all four affected intervals in the Rucio advisory.

  2. Apply the corrected release

    Move affected installations to an appropriate fixed release: 35.9.1, 38.6.1, 40.4.2, or 41.1.1. Select the release that matches the deployment's supported line.

  3. Verify the running version

    After deployment, inspect the version actually running on every Rucio service. Confirm it reaches the advisory's fixed threshold for that line and record the result.

  4. Investigate suspicious account activity

    Review authentication and privileged-action records for unexplained account use on previously affected services. Treat anomalies as leads for investigation, not proof that this CVE was exploited.

What Brandefense can do

Frequently Asked Questions

Can CVE-2026-100397 be used without a Rucio account?

Yes. Rucio's advisory says the challenge-token request needs no prior authentication and can name an account, including an administrator.

Does the ten-second challenge lifetime prevent account impersonation?

No. The advisory describes a ten-second opportunity to present the challenge as an authentication credential. Updating the affected Rucio release addresses the underlying token validation flaw.

Which Rucio releases fix CVE-2026-100397?

The advisory lists 35.9.1, 38.6.1, 40.4.2, and 41.1.1 as fixed releases. Match the target to the installed line and verify the running version after updating.

Sources

  1. Rucio: Unauthenticated administrator impersonation through SSH challenge tokensRucio / GitHub Security Advisory
  2. Known Exploited Vulnerabilities CatalogCISA
ShareLinkedInX
Brandefense logo

Stay Ahead of Digital Threats.

Take control of your digital security with an exclusive demo of our AI-driven threat intelligence platform.

Open The Full Demo Form →