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 #15262] Vulnerability responsible disclosure #56274

New Issue
Open
opened 2026-04-29 10:33:24 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-29 10:33:24 -05:00
Owner
Copy Link

Originally created by @CERT-PL-CNA on GitHub (Apr 3, 2026).
Original GitHub issue: https://github.com/ollama/ollama/issues/15262

Hi,
as CERT.PL CNA (CVE Numbering Authority) we were requested to assign CVEs for vulnerabilities found in in this project. The tester reported you the details through "Report a vulnerability" function and we mailed you at hello@ollama.com (from cert@cert.pl), both left with no reaction throughout last weeks.

We would like to know how should the vulnerabilities be reported so it's effective?
We are planning to publish the CVEs by the end of April 2026.

Originally created by @CERT-PL-CNA on GitHub (Apr 3, 2026). Original GitHub issue: https://github.com/ollama/ollama/issues/15262 Hi, as CERT.PL CNA (CVE Numbering Authority) we were requested to assign CVEs for vulnerabilities found in in this project. The tester reported you the details through "Report a vulnerability" function and we mailed you at hello@ollama.com (from cert@cert.pl), both left with no reaction throughout last weeks. We would like to know how should the vulnerabilities be reported so it's effective? We are planning to publish the CVEs by the end of April 2026.
GiteaMirror commented 2026-04-29 10:33:24 -05:00
Author
Owner
Copy Link

@CERT-PL-CNA commented on GitHub (Apr 23, 2026):

Hi,

In case of no answer from your side we will publish CVE entries according to information provided by the finder on 29.04.2026

<!-- gh-comment-id:4304681580 --> @CERT-PL-CNA commented on GitHub (Apr 23, 2026): Hi, In case of no answer from your side we will publish CVE entries according to information provided by the finder on 29.04.2026
GiteaMirror commented 2026-04-29 10:33:25 -05:00
Author
Owner
Copy Link

@CERT-PL-CNA commented on GitHub (Apr 29, 2026):

Hi

As mentioned before, we have published the CVEs:

https://cert.pl/en/posts/2026/04/CVE-2026-42248/

https://www.cve.org/CVERecord?id=CVE-2026-42248
https://www.cve.org/CVERecord?id=CVE-2026-42249

Kind regards,
CSIRT NASK / CERT Polska
cert.pl/en/

<!-- gh-comment-id:4343481071 --> @CERT-PL-CNA commented on GitHub (Apr 29, 2026): Hi As mentioned before, we have published the CVEs: https://cert.pl/en/posts/2026/04/CVE-2026-42248/ https://www.cve.org/CVERecord?id=CVE-2026-42248 https://www.cve.org/CVERecord?id=CVE-2026-42249 Kind regards, CSIRT NASK / CERT Polska cert.pl/en/
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
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#56274
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?