Skip to main content
Menu
CVEs

Sprout Track auth bypass via hardcoded JWT signing secret

Sprout Track before 1.3.5 falls back to a hardcoded, publicly known JWT signing secret when JWT_SECRET is not set; self-hosted deployments are the main concern. Fixed in 1.3.5.

CVE-2026-77338Published November 19, 2026, updated

9.3CriticalCNA
Exploited
No known exploitation
Fix
Fixed in 1.3.5
Who is exposed
Default setups

Summary

Sprout Track, a self-hosted baby tracking application, signs login tokens with a publicly known hardcoded secret when its JWT_SECRET setting is unset. An attacker can reach it remotely without logging in and forge tokens with arbitrary claims, including system-administrator claims, to access administrative functions and read or modify family, child activity, account, and email data.

Written by a model

Original 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.

Who should check

Teams self-hosting Sprout Track (Oak-and-Sprout sprout-track) on releases before v1.3.5 that do not set a unique JWT_SECRET.

“Affected versions: All releases prior to v1.3.5”

github.com

What to do

  1. Check every install: default setups are affected.

  2. Upgrade to a fixed version: 1.3.5.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-77338 (Sprout Track: Authentication bypass via default JWT signing secret), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-77338 (entry last updated 2026-11-19):
Affected:
- Oak-and-Sprout sprout-track: fixed in 1.3.5
Fixed versions: 1.3.5.
Conditions (all must be true for the bug to be hit):
- Sprout Track versions before 1.3.5 where the JWT_SECRET environment variable is not set, so the app falls back to a hardcoded public secret. (source: https://github.com/Oak-and-Sprout/sprout-track/security/advisories/GHSA-x6rw-w9f5-5hw2)
- Self-hosted deployments are the main concern; managed and hosted instances were remediated. (source: https://github.com/Oak-and-Sprout/sprout-track/security/advisories/GHSA-x6rw-w9f5-5hw2)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-77338 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-77338 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/Oak-and-Sprout/sprout-track/security/advisories/GHSA-x6rw-w9f5-5hw2
- https://github.com/Oak-and-Sprout/sprout-track/pull/200
- https://github.com/Oak-and-Sprout/sprout-track/commit/2b05592b089009d5a3b86b0769dcf3407a689c6a
- https://github.com/Oak-and-Sprout/sprout-track/releases/tag/1.3.5
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-77338
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-77338"}.

Affected versions

cve.now Index

35Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure25/25Default setups, CISA rates it automatable
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity10/10CVSS 9.3, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 75 if added to CISA KEV
  • Would score about 70 if CISA's SSVC rates exploitation active

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Posted on X by cve.now
  4. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: total

  5. Record last updated

Evidence 6

Questions about CVE-2026-77338

Is CVE-2026-77338 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

When the JWT_SECRET environment variable is not set, Sprout Track signs authentication tokens with a hardcoded, publicly known secret. Forged tokens, including system administrator tokens, can reach administrative functions and read or modify data across families and accounts, including child activity data and account email addresses.

Source: github.com

Which versions are affected by CVE-2026-77338?

sprout-track: before 1.3.5.

Source: cve.now feed data

Am I affected, and how do I check?

The issue affects Sprout Track versions before 1.3.5 where the JWT_SECRET environment variable is not set. Self-hosted deployments are the primary concern, since managed and hosted instances were remediated. To check, look at the installed version and whether JWT_SECRET is defined in the deployment environment.

Source: github.com

How do I fix CVE-2026-77338?

Update to v1.3.5 or later immediately.

Source: github.com

No corrections so far. Something wrong on this page? Report an error.