External risk intelligence

Sprout Track Hardcoded Secret Allows Unauthenticated Admin Access

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2026-77338

Sprout Track is a self-hosted application. While web applications can be exposed to the internet, they are frequently deployed in private, internal, or home-network environments for personal use. Because public internet exposure is not a standard design requirement or the default deployment pattern for this type of personal tracking software, it is classified as possible rather than likely or very likely.

Halo Surface Signal: 3 out of 5 — possibly public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A security vulnerability has been identified in the Sprout Track baby tracking application that could allow unauthorized access to sensitive family and account data. This issue arises from the use of a default, publicly known secret key for signing data, which can be exploited by attackers to gain administrative privileges on network-accessible instances if not properly secured with a unique secret.

  • Unprotected default secrets enable unauthorized administrative access.
  • Confirm relevance and exposure of self-hosted deployments.
  • Strong configuration protects sensitive personal and family data.

Attack Path

How an attacker could exploit the issue

An unauthenticated attacker can exploit this vulnerability if they can reach a Sprout Track deployment that uses a default or weak signing secret. By crafting a malicious JSON Web Token (JWT) with administrator privileges, the attacker can bypass authentication and gain access to sensitive family, child, account, and email data.

  • Network access to deployment required.
  • Attacker signs JWTs with admin claims.
  • Risk: Unauthorized access to sensitive data.

Live Threat

Current exploitation, exposure, and threat context

On a network-reachable Sprout Track deployment, an unauthenticated attacker could forge security tokens to gain administrative access. This would allow them to read or change sensitive family, child activity, account, and email data. Deployments using a strong, unique secret key are not affected, and managed or hosted instances have been fixed.

  • Family, child, and account data
  • Attacker signs tokens, gains admin access
  • Unauthorized data access and modification

Operational Fix

Recommended remediation, mitigation, and detection steps

For self-hosted applications like Sprout Track, the application owners are primarily responsible for addressing this vulnerability, with support from infrastructure or platform teams managing the underlying systems. The first practical step is to locate all instances of Sprout Track, determine their network reachability and business criticality, identify the accountable owner for each instance, and then plan remediation based on the assessed risk.

  • Application owners should address the issue.
  • Verify all Sprout Track deployments.
  • Plan remediation based on risk.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Sprout Track?

Sprout Track is a self-hosted software application designed for parents and caregivers to monitor and document a child's daily activities, health milestones, and personal family data. Because users host it themselves on their own servers or local hardware, they are responsible for the application's configuration and security settings, unlike software-as-a-service platforms that manage these security details automatically.

What does CVE-2026-77338 mean for my data?

This vulnerability is classified as CWE-798, which refers to the use of hardcoded credentials. In this case, Sprout Track relies on a default, publicly known signing secret if a user does not provide their own. An attacker can leverage this known secret to forge digital security tokens, allowing them to impersonate an administrator and gain unauthorized access to sensitive family records, child activity logs, and account settings.

How can an attacker trigger this vulnerability?

An attacker must have network access to the Sprout Track instance to exploit this bug. If the application is reachable over a network, the attacker can create and sign fraudulent JSON Web Tokens (JWTs) using the default secret to bypass authentication. Importantly, instances that have been manually configured with a strong, unique secret key are not vulnerable to this method of unauthorized access.

Do I need to worry if my Sprout Track is internal?

Halo Surface Signal indicates that while this is a critical issue, your risk depends on how the application is deployed. Since Sprout Track is often kept on private home or internal networks, it may not be reachable from the public internet. If your instance is strictly internal and inaccessible from outside your local environment, the risk of an external attacker reaching it is significantly reduced.

What should I do to secure my Sprout Track instance?

The most effective way to secure your instance is to update to version 1.3.5, which addresses this flaw. If you are self-hosting, verify that you have configured a unique, strong secret key for your JWT generation. Locate all instances you manage, check their network reachability, and ensure that your security configuration does not rely on default or publicly known values.

References