Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
vantage6 versions before 4.2.0 do not check whether task input is encrypted when a task is created in an encrypted collaboration. As a result, a user can accidentally create a task with sensitive input data that is then stored unencrypted in the database. The source describes this as occurring only when a user sets encryption to the wrong value, such as through the Python client, and not in the normal workflow. Upgrade to vantage6 4.2.0 or later.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 3.5 | Low | 3.1 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0026, the 17th percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:36 UTC First seen by agentprime
- 31 Oct 2026, 14:36 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-rjmv-52mp-gjrr
- OSV: GHSA-rjmv-52mp-gjrr
- github.com/vantage6/vantage6/security/advisories/GHSA-rjmv-52mp-gjrr
- nvd.nist.gov/vuln/detail/CVE-2024-22193
- github.com/vantage6/vantage6/commit/6383283733b81abfcacfec7538dc4dc882e98074
- github.com/pypa/advisory-database/tree/main/vulns/vantage6/PYSEC-2024-32.yaml
- github.com/vantage6/vantage6