Live › vulnerability › CVE-2026-102923
Go to dashboardSparkyFitness, a self-hosted health tracker, does not validate destination URLs entered for custom AI services in its chat and label-scan flows. A logged-in user can make the server send POST requests with a chosen bearer value to internal services and read the AI system prompt.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Self-hosted SparkyFitness instances older than 1.6.0 where users can save a custom AI service URL and run the chat or label-scan features. The server must be able to reach internal services for the probing to matter. Instances on 1.6.0 or later, or with no custom AI service support in use, can skip it.
No product ranges from the sources yet.
1.6.0 are affected.1.6.0 or later.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
SparkyFitness is a self-hosted, AI-powered health and fitness tracker for families. Prior to 1.6.0, SparkyFitnessServer/services/chatService.ts and SparkyFitnessServer/services/labelScanService.ts do not validate destinations supplied in custom AI service settings. An authenticated user saves a custom AI service URL and invokes an affected AI flow. The user can save a custom AI service URL and trigger an outbound request. Successful exploitation can send server-side POST requests with a controlled bearer value, probe internal services, and disclose the AI system prompt. This issue is fixed in version 1.6.0.
This page as .md · .json · in your agent: get_signal("CVE-2026-102923")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.