CVSS 3.1
10.0 criticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:HCritical (10.0) in rucio rucio. Fixed in rucio 35.9.1, 38.6.1, 40.4.2.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:Hrucio (PyPI): fixed in 35.9.1, 38.6.1, 40.4.2, 41.1.1Explain CVE-2026-100397 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-100397?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-100397?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-100397 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| rucio | >= 1.14.0, < 35.9.1 |
| rucio | >= 36.0.0, < 38.6.1 |
| rucio | >= 39.0.0, < 40.4.2 |
| rucio | >= 41.0.0, < 41.1.1 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-x585-4vv8-2mh2 | PyPI | rucio | >=1.14.0.post1 <35.9.1 | 35.9.1 |
| GHSA-x585-4vv8-2mh2 | PyPI | rucio | >=36.0.0rc1 <38.6.1 | 38.6.1 |
| GHSA-x585-4vv8-2mh2 | PyPI | rucio | >=39.0.0rc1 <40.4.2 | 40.4.2 |
| GHSA-x585-4vv8-2mh2 | PyPI | rucio | >=41.0.0rc1 <41.1.1 | 41.1.1 |
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.