CVE-2026-85391: Peppermint through 0.5.5 Use of Hard-coded JWT Signing Secret in docker-compose.yml

Published Sep 3, 2026
·
Updated

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.

Affected Software

1 affected component
Peppermint<=0.5.5

Event History

Sep 3, 2026
CVE Published
via MITRE·06:54 PM
Data Sourced
via MITRE·06:54 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are exposed?

Peppermint versions through 0.5.5 are affected when they use the hardcoded JWT signing secret present in docker-compose.yml. The provided data does not identify any configuration-specific exception.

2

What does an attacker need to exploit this issue?

An attacker does not need credentials or user interaction. They can use the published signing secret to create valid session tokens for arbitrary user IDs and access protected endpoints.

3

What level of access can a forged token provide?

A forged token can impersonate any account because the attacker can mint tokens for arbitrary user IDs. This enables access to protected endpoints without legitimate credentials.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203