PYSEC-2026-1295
Vulnerability from pysec - Published: 2026-07-07 11:45 - Updated: 2026-07-07 17:24Impact
During the proxy generation process (e.g., when using dirac-proxy-init) it is possible for unauthorized users on the same machine to gain read access to the proxy. This allows the user to then perform any action that is possible with the original proxy.
This vulnerability only exists for a short period of time (sub-millsecond) during the generation process.
Patches
Has the problem been patched? What versions should users upgrade to?
Workarounds
Setting the X509_USER_PROXY environment variable to a path that is inside a directory that is only readable to the current user avoids the potential risk. After the file has been written it can be safely copied to the standard location (/tmp/x509up_uNNNN).
References
| Name | purl | dirac | pkg:pypi/dirac |
|---|
{
"affected": [
{
"package": {
"ecosystem": "PyPI",
"name": "dirac",
"purl": "pkg:pypi/dirac"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "8.0.41"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"7.2.0",
"7.2.0a32",
"7.2.0a33",
"7.2.0a34",
"7.2.0a35",
"7.2.0a36",
"7.2.0a38",
"7.2.0a39",
"7.2.1",
"7.2.10",
"7.2.12",
"7.2.13",
"7.2.14",
"7.2.15",
"7.2.16",
"7.2.19",
"7.2.2",
"7.2.20",
"7.2.21",
"7.2.22",
"7.2.23",
"7.2.24",
"7.2.25",
"7.2.26",
"7.2.27",
"7.2.28",
"7.2.3",
"7.2.30",
"7.2.31",
"7.2.32",
"7.2.33",
"7.2.34",
"7.2.35",
"7.2.36",
"7.2.37",
"7.2.38",
"7.2.39",
"7.2.4",
"7.2.40",
"7.2.41",
"7.2.42",
"7.2.43",
"7.2.44",
"7.2.45",
"7.2.46",
"7.2.47",
"7.2.48",
"7.2.49",
"7.2.5",
"7.2.50",
"7.2.51",
"7.2.52",
"7.2.6",
"7.2.7",
"7.2.8",
"7.2.9",
"7.2a29",
"7.3.0a10",
"7.3.0a11",
"7.3.0a13",
"7.3.0a14",
"7.3.0a15",
"7.3.0a16",
"7.3.0a17",
"7.3.0a18",
"7.3.0a19",
"7.3.0a2",
"7.3.0a20",
"7.3.0a21",
"7.3.0a22",
"7.3.0a23",
"7.3.0a24",
"7.3.0a3",
"7.3.0a4",
"7.3.0a5",
"7.3.0a6",
"7.3.0a7",
"7.3.0a8",
"7.3.0a9",
"7.3.1",
"7.3.10",
"7.3.11",
"7.3.12",
"7.3.13",
"7.3.14",
"7.3.15",
"7.3.16",
"7.3.17",
"7.3.18",
"7.3.19",
"7.3.2",
"7.3.20",
"7.3.21",
"7.3.22",
"7.3.23",
"7.3.24",
"7.3.26",
"7.3.27",
"7.3.28",
"7.3.29",
"7.3.3",
"7.3.30",
"7.3.31",
"7.3.32",
"7.3.33",
"7.3.34",
"7.3.35",
"7.3.36",
"7.3.37",
"7.3.38",
"7.3.4",
"7.3.5",
"7.3.6",
"7.3.7",
"7.3.8",
"7.3.9",
"7.4.0a1",
"8.0.0",
"8.0.0a1",
"8.0.0a10",
"8.0.0a11",
"8.0.0a12",
"8.0.0a13",
"8.0.0a14",
"8.0.0a15",
"8.0.0a16",
"8.0.0a17",
"8.0.0a18",
"8.0.0a19",
"8.0.0a20",
"8.0.0a21",
"8.0.0a22",
"8.0.0a23",
"8.0.0a24",
"8.0.0a25",
"8.0.0a26",
"8.0.0a27",
"8.0.0a28",
"8.0.0a29",
"8.0.0a5",
"8.0.0a6",
"8.0.0a7",
"8.0.0a8",
"8.0.0a9",
"8.0.1",
"8.0.10",
"8.0.11",
"8.0.12",
"8.0.13",
"8.0.14",
"8.0.15",
"8.0.16",
"8.0.17",
"8.0.18",
"8.0.19",
"8.0.2",
"8.0.20",
"8.0.21",
"8.0.22",
"8.0.23",
"8.0.24",
"8.0.25",
"8.0.26",
"8.0.27",
"8.0.28",
"8.0.29",
"8.0.3",
"8.0.30",
"8.0.31",
"8.0.32",
"8.0.33",
"8.0.34",
"8.0.35",
"8.0.36",
"8.0.37",
"8.0.38",
"8.0.39",
"8.0.4",
"8.0.40",
"8.0.5",
"8.0.6",
"8.0.7",
"8.0.8",
"8.0.9"
]
}
],
"aliases": [
"CVE-2024-29905",
"GHSA-v6f3-gh5h-mqwx"
],
"details": "### Impact\n\nDuring the proxy generation process (e.g., when using `dirac-proxy-init`) it is possible for unauthorized users on the same machine to gain read access to the proxy. This allows the user to then perform any action that is possible with the original proxy.\n\nThis vulnerability only exists for a short period of time (sub-millsecond) during the generation process.\n\n### Patches\n\n_Has the problem been patched? What versions should users upgrade to?_\n\n### Workarounds\n\nSetting the `X509_USER_PROXY` environment variable to a path that is inside a directory that is only readable to the current user avoids the potential risk. After the file has been written it can be safely copied to the standard location (`/tmp/x509up_uNNNN`).\n\n### References",
"id": "PYSEC-2026-1295",
"modified": "2026-07-07T17:24:00.495476Z",
"published": "2026-07-07T11:45:37.723803Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/DIRACGrid/DIRAC/security/advisories/GHSA-v6f3-gh5h-mqwx"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-29905"
},
{
"type": "WEB",
"url": "https://github.com/DIRACGrid/DIRAC/commit/1faa709341969a6321e29c843ca94039d33b2c3d"
},
{
"type": "PACKAGE",
"url": "https://github.com/DIRACGrid/DIRAC"
},
{
"type": "PACKAGE",
"url": "https://pypi.org/project/dirac"
},
{
"type": "ADVISORY",
"url": "https://github.com/advisories/GHSA-v6f3-gh5h-mqwx"
}
],
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:L",
"type": "CVSS_V3"
}
],
"summary": "DIRAC: Unauthorized users can read proxy contents during generation"
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.