← back to feed
CVE-2026-100397

CVE-2026-100397

validatingZero is analyzing and reversing it now.

GHSA-x585-4vv8-2mh2 ↗

no check availablenot proven exploitable
awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
pip:rucio >= 1.14.0.post1, < 35.9.1; >= 36.0.0rc1, < 38.6.1; >= 39.0.0rc1, < 40.4.2; >= 41.0.0rc1, < 41.1.1
fixed in 35.9.1, 38.6.1, 40.4.2, 41.1.1
ETK-2026-4337Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:pypi/rucio
cvss9.8cna vendorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
–running
startingcurrent stage
timeline
0 = trigger signal
trigger signal +0m
0
+5min
+10min
+15min
+20min

description

Affected Rucio deployments may accept SSH challenge tokens as API authentication credentials. An unauthenticated attacker can obtain a challenge token for a selected account and use it to act as that account during the token's validity period. Exposure requires the affected SSH challenge-token functionality to be reachable.

Still under analysis: more detail becomes available as the pipeline runs.

mitigation

Upgrade pip:rucio to 35.9.1, 38.6.1, 40.4.2, or 41.1.1, as appropriate for the deployed release line. Until upgraded, restrict access to the SSH challenge-token endpoint and the Rucio API to trusted clients.

fixed in 35.9.1, 38.6.1, 40.4.2, 41.1.1

check
building now
exploit
not yet
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
–
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
–
cve.org record, t = 0The moment cve.org publishes the CVE in full.
not published yet
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Run in progress: no artifact yet.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-11-13 01:09Z
    ghsa: trigger signal, started the run
    https://github.com/advisories/GHSA-x585-4vv8-2mh2

this entry in the feed

GET /api/v1/feed/CVE-2026-100397

{
  "etk_id": "ETK-2026-4337",
  "cve_id": "CVE-2026-100397",
  "display_id": "CVE-2026-100397",
  "ghsa_id": "GHSA-x585-4vv8-2mh2",
  "euvd_id": null,
  "status": "in_pipeline",
  "anchor_state": "awaiting_cve",
  "title": "Authentication bypass through SSH challenge tokens in Rucio",
  "summary": "Affected Rucio deployments may accept SSH challenge tokens as API authentication credentials. An unauthenticated attacker can obtain a challenge token for a selected account and use it to act as that account during the token's validity period. Exposure requires the affected SSH challenge-token functionality to be reachable.",
  "mitigation": "Upgrade pip:rucio to 35.9.1, 38.6.1, 40.4.2, or 41.1.1, as appropriate for the deployed release line. Until upgraded, restrict access to the SSH challenge-token endpoint and the Rucio API to trusted clients.",
  "vendor": null,
  "product": "pip:rucio",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 1.14.0.post1, < 35.9.1"
      ],
      "ecosystem": "pip",
      "fixed_versions": [
        "35.9.1"
      ],
      "package_name": "rucio",
      "purl": "pkg:pypi/rucio"
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 36.0.0rc1, < 38.6.1"
      ],
      "ecosystem": "pip",
      "fixed_versions": [
        "38.6.1"
      ],
      "package_name": "rucio",
      "purl": "pkg:pypi/rucio"
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 39.0.0rc1, < 40.4.2"
      ],
      "ecosystem": "pip",
      "fixed_versions": [
        "40.4.2"
      ],
      "package_name": "rucio",
      "purl": "pkg:pypi/rucio"
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 41.0.0rc1, < 41.1.1"
      ],
      "ecosystem": "pip",
      "fixed_versions": [
        "41.1.1"
      ],
      "package_name": "rucio",
      "purl": "pkg:pypi/rucio"
    }
  ],
  "cwes": null,
  "cvss_score": 9.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": null,
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": null,
  "t0_at": null,
  "signals": {
    "trigger_signal": {
      "at": "2026-11-13T01:09:54+00:00",
      "days": -0.014990987129629629,
      "is_lower_bound": true,
      "measured_at": "2026-11-13T01:31:29.290805+00:00",
      "url": "https://github.com/advisories/GHSA-x585-4vv8-2mh2"
    }
  }
}

published 2026-11-13 01:27Z
last change 2026-11-13 01:27Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.

Protected by reCAPTCHA; the Google Privacy Policy and Terms of Service apply.