{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-102923 exists.","fix":"No fix has been published for CVE-2026-102923 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-102923 is a medium-severity server-side request forgery vulnerability in CodeWithCJ SparkyFitness, published on 16 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-102923 and fix it if it is affected.\n\nWhat it is: CVE-2026-102923 is a medium-severity server-side request forgery vulnerability in CodeWithCJ SparkyFitness, published on 16 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-102923 exists.\n\nAffected product: CodeWithCJ SparkyFitness. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-102923/ (Markdown: https://insights.sbomify.com/CVE-2026-102923/index.md)","id":"CVE-2026-102923","markdown":"https://insights.sbomify.com/CVE-2026-102923/index.md","name":"CVE-2026-102923","record":{"aliases":["GHSA-rmxj-43xh-mcm3"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Self-hosted fitness tracker","requires_auth":"low_privilege","summary":"An authenticated user can trigger server-side requests to internal services via unvalidated custom AI URLs, potentially disclosing sensitive data.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"SparkyFitness: SSRF via unvalidated custom_url in AI service settings","id":"CVE-2026-102923","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"virtualenv bash and fish activation scripts execute commands embedded in paths","id":"CVE-2026-102925"},"packages":[],"prev":{"headline":"IBM i is Affected By An Improper Privilege Management Vulnerability","id":"CVE-2026-102917"},"products":["SparkyFitness"],"published":"2026-10-16","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-28","vendors":["CodeWithCJ"]},"summary":"An authenticated user can trigger server-side requests to internal services via unvalidated custom AI URLs, potentially disclosing sensitive data.","url":"https://insights.sbomify.com/CVE-2026-102923/"}