CVE-2026-77338
Received Received - Intake

Hardcoded JWT Secret in Sprout Track

Vulnerability report for CVE-2026-77338, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-19

Last updated on: 2026-11-19

Assigner: GitHub, Inc.

Description

Sprout Track is a self-hosted baby tracking application. Prior to 1.3.5, Sprout Track uses a publicly known hardcoded signing secret when JWT_SECRET is unset, and standard setup does not generate a unique secret. On a network-reachable affected deployment, an unauthenticated attacker can sign JWTs with arbitrary claims, including system-administrator claims, to access administrative functionality and read or modify family, child activity, account, and email data. Deployments with a strong unique JWT_SECRET are not affected. Managed and hosted instances were reported remediated. This issue is fixed in version 1.3.5.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-19
Last Modified
2026-11-19
Generated
2026-11-20
AI Q&A
2026-11-20
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
sprout_track sprout_track to 1.3.5 (exc)
oak_and_sprout sprout_track 1.3.5

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-798 The product contains hard-coded credentials, such as a password or cryptographic key.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

Sprout Track is a self-hosted baby tracking app. Prior to version 1.3.5, it used a hardcoded default JWT signing secret when the JWT_SECRET environment variable was not set. This allowed attackers to forge authentication tokens, including system-administrator claims, and gain unauthenticated access to sensitive data.

Detection Guidance

Check if your Sprout Track instance is running a version prior to 1.3.5 by inspecting the version in the application or logs. Verify if JWT_SECRET is explicitly configured in your environment or deployment settings. Look for unusual authentication attempts or unauthorized access to administrative features.

Impact Analysis

Unauthenticated attackers could access administrative functions and read or modify family, child activity, account, and email data. Deployments without a unique JWT_SECRET were fully exposed to this risk.

Mitigation Strategies

Upgrade Sprout Track to version 1.3.5 or later immediately. Ensure JWT_SECRET is set to a strong, unique value in your environment. Invalidate all existing sessions after upgrading. Verify configuration and access controls post-upgrade.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-77338. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...