michaelfeil / michaelfeil/infinity
allow transformers>=5.0.0rc3 to fix reported CVEs
- Dominant language
- Python
- Stars
- 2.9k
- Forks
- 206
- PR merge metrics
- No merged PRs in 30d
Description
infinity-emb[torch] currently prevents downstream projects from resolving to the transformers version that fixes 2 CVEs.
Current dependency chain:
infinity-emb==0.0.77
-> sentence-transformers>=3.0.1,<4.0.0
-> transformers>=4.41.0,<5.0.0
The following high-CVSS vulnerabilities exist against transformers==4.57.6:
CVE-2026-1839, fixed by transformers>=5.0.0rc3.
CVE-2025-14929, fixed by transformers>=5.0.0rc3.
Because sentence-transformers<4.0.0 requires transformers>=4.41.0,<5.0.0, consumers of infinity-emb[torch] cannot resolve to transformers>=5.0.0rc3.
Could infinity-emb relax or update its dependency constraints to allow a newer sentence-transformers line that supports Transformers 5.x? For example, sentence-transformers==5.5.1 declares transformers>=4.41.0,<6.0.0.
A possible dependency update could be sentence-transformers>=5.0.0,<6.0.0, or another compatible range that allows transformers>=5.0.0rc3.
Without this change, downstream users cannot resolve these transformers CVEs through normal dependency resolution while continuing to use infinity-emb[torch].
Contributor guide
No contributing guide indexed for this repository
Research direction
Inspect the dependency declaration for infinity-emb[torch] and compare the supported sentence-transformers 5.x and transformers 5.x ranges described in the issue. Verify dependency resolution with transformers>=5.0.0rc3; done means downstream users can install the package while resolving versions that include both CVE fixes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- machine-learning, security
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100