mirror of
https://github.com/binwiederhier/ntfy.git
synced 2026-05-09 16:35:53 +02:00
[GH-ISSUE #1513] CVE-2025-55182 #1066
Labels
No labels
ai-generated
android-app
android-app
android-app
🪲 bug
build
build
dependencies
docs
enhancement
enhancement
🔥 HOT
in-progress 🏃
ios
prio:low
prio:low
pull-request
question
🔒 security
server
server
unified-push
web-app
website
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ntfy#1066
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
Originally created by @canuckdev on GitHub (Dec 8, 2025).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1513
Hi,
I'm using latest ntfy release:
ntfy 2.15.0 (
b531bc9), runtime go1.24.10, built at 2025-11-16T18:48:15Zbut from the js console I see:
and 19.2.0 is vulnerable according to CVE record https://www.cve.org/CVERecord?id=CVE-2025-55182.
What do you think?
Thanks, Jeremy
@canuckdev commented on GitHub (Dec 8, 2025):
https://react.dev/blog/2025/12/03/critical-security-vulnerability-in-react-server-components
@binwiederhier commented on GitHub (Dec 8, 2025):
My understanding is that the CVE only applies if you use React on the server side. ntfy does not run React on the server. It's 100% Go.
That makes it not vulnerable. Or am I misunderstanding the CVE?
@canuckdev commented on GitHub (Dec 8, 2025):
I don't know enough about ntfy web app and react, but the react.dev blog post says:
@itepechi commented on GitHub (Dec 10, 2025):
github.com/binwiederhier/ntfy@b531bc95ea/server/server.go (L566-L569)As mentioned, the server is written in Go, and the frontend is a static webpage. The CVE only applies if your server is capable of running a React code (a JavaScript library).
@canuckdev commented on GitHub (Dec 11, 2025):
Thank you :)