Skip to main content
VulnerabilityPublished

CVE-2026-77338: Oak-and-Sprout sprout-track · Use of Hard-coded Credentials

Affects Oak-and-Sprout sprout-trackSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.3 Critical : upgrade to 1.3.5 as a priority.

Data as of 19 Nov 2026, 17:06 UTC

CVSS 4.0 base score
9.3Critical
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 4.09.3
Patch
Available – fixed in 1.3.5
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.

What to do

Upgrade Oak-and-Sprout sprout-track to 1.3.5.

Affected software

ProductAffectedFixed in
Oak-and-Sproutsprout-trackAffected
  • <1.3.5
Fixed in
  • 1.3.5

AI-suggested

Upgrade all affected Sprout Track deployments to version 1.3.5 or later, which fixes the hardcoded credential issue. Alternatively, ensure that a strong, unique JWT_SECRET environment variable is set to override the default hardcoded secret. Managed and hosted instances have already been remediated by the vendor.

Description

Sprout Track versions prior to 1.3.5 use a publicly known hardcoded signing secret if the JWT_SECRET environment variable is not set. This allows unauthenticated attackers on network-reachable deployments to create JWTs with arbitrary claims, including administrative privileges, enabling unauthorized access to sensitive data and administrative functions. The issue is fixed in version 1.3.5. Deployments with a unique JWT_SECRET are not affected, and managed hosted instances have been remediated.

References

Community reviews

Loading reviews…