Lobe Chat Desktop vulnerable to Remote Code Execution via XSS in Chat Messages
osv · CVE-2025-59417
npm: @lobehub/chat
No access to your tenant or devices. Every item links to its source. What this means
Security
Microsoft security updates and public advisory evidence: affected products, fixing updates, exploitation and source coverage.
Public source statements across vendors. Explicit aliases connect records; each publisher keeps its own state, severity and affected-version evidence.
osv · CVE-2025-59417
npm: @lobehub/chat
osv · CVE-2025-54468 · GO-2025-3982
Go: github.com/rancher/rancher · Go: github.com/rancher/rancher · Go: github.com/rancher/rancher
osv · RUSTSEC-2025-0071
crates.io: ammonia · crates.io: ammonia · crates.io: ammonia
osv · CVE-2025-59342 · GO-2025-3967
Go: github.com/esm-dev/esm.sh
osv · CVE-2025-58751
npm: vite · npm: vite · npm: vite
osv · CVE-2025-10954 · GO-2025-3987
Go: github.com/nyaruka/phonenumbers
osv · CVE-2025-57319
npm: fast-redact
osv · CVE-2025-56200
npm: validator
osv · CVE-2025-58063 · GO-2025-3942
Go: github.com/coredns/coredns
osv · CVE-2025-59341 · GO-2025-3962
Go: github.com/esm-dev/esm.sh
osv · BIT-argo-cd-2025-55190 · CVE-2025-55190 · GO-2025-3934
Go: github.com/argoproj/argo-cd/v2 · Go: github.com/argoproj/argo-cd/v2 · Go: github.com/argoproj/argo-cd/v3
osv · CVE-2025-59834
npm: adb-mcp
osv · CVE-2025-59046
npm: interactive-git-checkout
osv · CVE-2025-58754
npm: axios · npm: axios
osv · CVE-2025-9910
npm: jsondiffpatch
osv · CVE-2025-58160 · RUSTSEC-2025-0055
crates.io: tracing-subscriber
osv · CVE-2025-55173
npm: next · npm: next
osv · CVE-2025-8959 · GO-2025-3892
Go: github.com/hashicorp/go-getter
osv · CVE-2025-54801 · GO-2025-3845
Go: github.com/gofiber/fiber/v2
osv · CVE-2025-54467 · GO-2025-3919
Go: github.com/neuvector/neuvector
osv · BIT-dotnet-2025-21176 · BIT-dotnet-sdk-2025-21176 · CVE-2025-21176
NuGet: Microsoft.NetCore.App.Runtime.linux-arm · NuGet: Microsoft.NetCore.App.Runtime.linux-arm64 · NuGet: Microsoft.NetCore.App.Runtime.linux-musl-arm
osv · BIT-vault-2025-6014 · CVE-2025-6014 · GO-2025-3841
Go: github.com/hashicorp/vault
osv · BIT-vault-2025-6015 · CVE-2025-6015 · GO-2025-3842
Go: github.com/hashicorp/vault
osv · CVE-2025-55159 · RUSTSEC-2025-0047
crates.io: slab
osv · BIT-vault-2025-6000 · CVE-2025-6000 · GO-2025-3838
Go: github.com/hashicorp/vault
osv · CVE-2025-54386 · GO-2025-3835
Go: github.com/traefik/traefik/v2 · Go: github.com/traefik/traefik/v3 · Go: github.com/traefik/traefik/v3
osv · CVE-2025-54799 · GO-2025-3847
Go: github.com/go-acme/lego · Go: github.com/go-acme/lego/v3 · Go: github.com/go-acme/lego/v4
osv · CVE-2025-54387
npm: ipx · npm: ipx · npm: ipx
osv · BIT-vault-2025-6004 · CVE-2025-6004 · GO-2025-3840
Go: github.com/hashicorp/vault
osv · CVE-2025-7054
crates.io: quiche
osv · BIT-vault-2025-6011 · CVE-2025-6011 · GO-2025-3839
Go: github.com/hashicorp/vault
osv · CVE-2025-58058 · GO-2025-3922
Go: github.com/ulikunitz/xz
osv · CVE-2025-54804
crates.io: russh
osv · CVE-2025-57752
npm: next · npm: next
osv · BIT-helm-2025-55198 · CVE-2025-55198 · GO-2025-3888
Go: helm.sh/helm/v3
osv · CVE-2025-9287
npm: cipher-base
osv · CVE-2025-53884 · GO-2025-3917
Go: github.com/neuvector/neuvector
osv · RUSTSEC-2024-0443
crates.io: webp
osv · CVE-2025-54424 · GO-2025-3834
Go: github.com/1Panel-dev/1Panel/core · Go: github.com/1Panel-dev/1Panel/core
osv · BIT-vault-2025-6013 · CVE-2025-6013 · GO-2025-3848
Go: github.com/hashicorp/vault
osv · CVE-2025-9288
npm: sha.js
osv · BIT-helm-2025-55199 · CVE-2025-55199 · GO-2025-3887
Go: helm.sh/helm/v3
osv · BIT-vault-2025-5999 · CVE-2025-5999 · GO-2025-3837
Go: github.com/hashicorp/vault
osv · BIT-vault-2025-6037 · CVE-2025-6037 · GO-2025-3836
Go: github.com/hashicorp/vault
osv · CVE-2025-5187 · GO-2025-3915
Go: k8s.io/kubernetes · Go: k8s.io/kubernetes · Go: k8s.io/kubernetes
osv · CVE-2025-54798
npm: tmp
osv · CVE-2025-51471 · GO-2025-3824
Go: github.com/ollama/ollama
osv · CVE-2025-57822
npm: next · npm: next
osv · CVE-2025-11065 · GO-2025-3900
Go: github.com/go-viper/mapstructure/v2
A catalog match establishes published evidence, not applicability to your environment. Check resolved package dependencies, or open a Microsoft CVE for fixing KBs, releases and planning.