github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-05-08 00:51:34 -05:00
Code Issues 14.5k Packages Projects Releases 120 Wiki Activity

[GH-ISSUE #8137] golang.org/x/crypto version in go.mod has critical CVE #51705

New Issue
Closed
opened 2026-04-28 20:46:46 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-28 20:46:46 -05:00
Owner
Copy Link

Originally created by @pivotal-marcela-campo on GitHub (Dec 17, 2024).
Original GitHub issue: https://github.com/ollama/ollama/issues/8137

What is the issue?

Using grype on Ollama's binary (latest version) yields CVE-2024-45337: x/crypto/ssh: misuse of ServerConfig.PublicKeyCallback may cause authorization bypass

go-module: golang.org/x/crypto (v0.23.0) identified via go-module-buildinfo-entry

Whilst this is actually not regarded as an issue in the crypto library by the golang community , it still appears on widely used scanners as such and it would be nice to get fixed.
Mitigation is available in crypto library version 0.31.0

OS

No response

GPU

No response

CPU

No response

Ollama version

0.5.3

Originally created by @pivotal-marcela-campo on GitHub (Dec 17, 2024). Original GitHub issue: https://github.com/ollama/ollama/issues/8137 ### What is the issue? Using grype on Ollama's binary (latest version) yields [CVE-2024-45337]( https://nvd.nist.gov/vuln/detail/CVE-2024-45337): **x/crypto/ssh: misuse of ServerConfig.PublicKeyCallback may cause authorization bypass** go-module: golang.org/x/crypto (v0.23.0) identified via go-module-buildinfo-entry Whilst this is actually not regarded as an issue in the crypto library [by the golang community](https://github.com/golang/go/issues/70779) , it still appears on widely used scanners as such and it would be nice to get fixed. Mitigation is available in crypto library version 0.31.0 ### OS _No response_ ### GPU _No response_ ### CPU _No response_ ### Ollama version 0.5.3
GiteaMirror added the bug label 2026-04-28 20:46:46 -05:00
GiteaMirror commented 2026-04-28 20:46:48 -05:00
Author
Owner
Copy Link

@aryaksudheer commented on GitHub (Dec 19, 2024):

It will be helpful to get this fix, as the CVE vulnerability is being flagged in security scans.

<!-- gh-comment-id:2553369627 --> @aryaksudheer commented on GitHub (Dec 19, 2024): It will be helpful to get this fix, as the CVE vulnerability is being flagged in security scans.
GiteaMirror commented 2026-04-28 20:46:48 -05:00
Author
Owner
Copy Link

@pdevine commented on GitHub (Dec 20, 2024):

Fixed in #8172

<!-- gh-comment-id:2557763959 --> @pdevine commented on GitHub (Dec 20, 2024): Fixed in #8172
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
amd
api
app
bug
build
cli
cloud
compatibility
context-length
create
docker
documentation
embeddings
feature request
feedback wanted
good first issue
gpt-oss
gpu
harmony
help wanted
image
install
intel
js
launch
linux
macos
memory
mlx
model
needs more info
networking
nvidia
ollama.com
performance
pull-request
Mirrored from GitHub Pull Request
 python
question
registry
rendering
thinking
tools
top
vulkan
windows
wsl
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#51705
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?