CVE-2026-79785 json
X-AnyLabeling before 4.0.0-beta.9 Improper Certificate Validation in Model Downloads
published 2026-08-25 2 mo ago modified 2026-09-24 45 d ago also EUVD-2026-65595
- cvss
- 5.9
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 20%
- public exploits
- 0
- none known
Summary
X-AnyLabeling's model downloader disabled TLS certificate verification. download_with_retry in anylabeling/services/auto_labeling/model.py built a context with ssl._create_unverified_context() and passed it to urllib.request.urlopen, so neither the certificate chain nor the hostname was checked on any model download, and models are fetched over HTTPS from the project's release host. Any party positioned to intercept that connection could therefore answer it with content of their own choosing. The response is written to a .part file and moved into place with os.replace, and the only post-download check, safe_check_model, validates the file's format rather than its provenance: no hash or signature is compared against an expected value. For an ONNX target the substituted file passes onnx.checker.check_model and is then used for inference, so the attacker chooses the model that produces the application's annotations. For a .pth or .pt target, which the shipped SAM2 video, YOLOE, UPN and open_vision configurations use, the check worker calls torch.load without weights_only, so a substituted file is unpickled and executes code of the attacker's choosing on PyTorch releases predating the weights_only default.
Patch / fix
- CVHub520 X-AnyLabeling 4.0.0-beta.9, 4.0.0b9
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 mo ago
Exploit prediction
0.28% chance of exploitation in the next 30 days, higher than 20% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 8.2 | CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N |
| CNA | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N |
| CNA | 4.0 | 8.2 | CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
Affected products
- CVHub520 X-AnyLabeling
Classification
- Weakness
-
- CWE-295 Improper Certificate Validation
References
-
github.com
/CVHub520/X-AnyLabeling/commit/52f7c30333f3f99711f09334d740212aa30b9958
patch
-
github.com
/CVHub520/X-AnyLabeling
product
-
github.com
/CVHub520/X-AnyLabeling/releases/tag/v4.0.0-beta.9
release-notes
-
github.com
/CVHub520/X-AnyLabeling/blob/v4.0.0-beta.8/anylabeling/services/auto_labeling/model.py
technical-description
-
pypi.org
/project/x-anylabeling-cvhub/
product
-
vulncheck.com
/advisories/x-anylabeling-before-4.0.0-beta.9-improper-certificate-validation-in-model-downloads
third-party-advisory
Sources
- CVE List CVE-2026-79785
- NVD CVE-2026-79785
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.