Description
Peppermint through 0.5.5 contains a hardcoded JWT signing secret in docker-compose.yml that allows unauthenticated attackers to forge session tokens for any account. Attackers can use the published secret to mint valid tokens for arbitrary user IDs and access protected endpoints without credentials.
Published: 2026-09-03
Score: 9.3 Critical
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

This vulnerability arises from a hardcoded JWT signing secret embedded in the docker-compose.yml file of Peppermint. An attacker who can access the publicly available source code can retrieve this secret and use it to generate valid JSON Web Tokens for any user ID. The forged tokens grant the attacker the same level of access as an authenticated user, enabling unauthorized use of protected endpoints and potential data theft or manipulation. The CVSS score of 9.3 marks it as a high‑severity flaw that can be exploited without any authentication.

Affected Systems

The issue affects the Peppermint open‑source project maintained by Peppermint‑Lab, specifically versions up through and including 0.5.5. Users running any of these releases are exposed to the risk of token forgery because the secret is stored in plain text within the docker-compose configuration.

Risk and Exploitability

Given the lack of an EPSS value, the exploit probability is not quantified, but the flaw is trivial to exploit: the secret is in a public repository and can be read by anyone. The CVSS score indicates maximum impact, and the vulnerability is not listed in the CISA KEV catalog, though its severity warrants immediate attention. Attackers can achieve full impersonation of any account without interacting with the application or possessing valid credentials.

Generated by OpenCVE AI on September 3, 2026 at 21:16 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Apply the latest Peppermint release that removes the hard‑coded JWT signing secret and replaces it with an environment‑configured value.
  • If an upgrade is not yet possible, edit docker‑compose.yml to override the signing secret with a strong, unique value stored in a secure secret management system and restrict file access to the deployment servers.
  • Verify that the deployment environment no longer contains the hard‑coded secret by scanning the repository and Dockerfiles for potential residual secrets and removing them.

Generated by OpenCVE AI on September 3, 2026 at 21:16 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Thu, 03 Sep 2026 20:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}


Thu, 03 Sep 2026 19:00:00 +0000

Type Values Removed Values Added
Description Peppermint through 0.5.5 contains a hardcoded JWT signing secret in docker-compose.yml that allows unauthenticated attackers to forge session tokens for any account. Attackers can use the published secret to mint valid tokens for arbitrary user IDs and access protected endpoints without credentials.
Title Peppermint through 0.5.5 Use of Hard-coded JWT Signing Secret in docker-compose.yml
First Time appeared Peppermint
Peppermint peppermint
Weaknesses CWE-798
CPEs cpe:2.3:a:peppermint:peppermint:*:*:*:*:*:*:*:*
Vendors & Products Peppermint
Peppermint peppermint
References
Metrics cvssV3_1

{'score': 9.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}

cvssV4_0

{'score': 9.3, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N'}


Subscriptions

Peppermint Peppermint
cve-icon MITRE

Status: PUBLISHED

Assigner: VulnCheck

Published:

Updated: 2026-09-03T19:00:50.811Z

Reserved: 2026-09-03T18:10:51.946Z

Link: CVE-2026-85391

cve-icon Vulnrichment

Updated: 2026-09-03T19:00:44.932Z

cve-icon NVD

Status : Received

Published: 2026-09-03T19:17:30.830

Modified: 2026-09-03T20:17:28.467

Link: CVE-2026-85391

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-03T21:30:06Z

Weaknesses
  • CWE-798

    Use of Hard-coded Credentials