High severityPythonHardcoded SecretsMEDIUM confidence
Hardcoded JWT Signing Secret
A JWT is signed or verified with a hardcoded secret literal (CWE-798).
Standards mapping
- OWASP Top 10
- A02:2021 - Cryptographic Failures
- OWASP ASVS
- V6.4.1 (L2)V3.5.3 (L1)
Vulnerable vs. safe
Flagged by this check
return jwt.encode(payload, "mySuperSecretSigningKey", algorithm="HS256")Passes - the safe pattern
return jwt.encode(payload, os.environ["JWT_SECRET"], algorithm="HS256")Why it matters & how to fix it
A JWT is signed or verified with a hardcoded secret literal (CWE-798). Anyone with the source can forge valid tokens. Load the signing secret from the environment or a secrets manager and rotate the exposed value.
References
Rule ID integsec-python-hardcoded-jwt-signing-secret - engine: Opengrep - license: MIT - Copyright (c) IntegSec Inc.
TurboPentest runs this check automatically
Connect a GitHub repo and this check runs on every white-box pentest - AI-validated and reported with proof, from $99 per target.
Start a pentestRelated checks
- JavaScript / TypeScript - Hardcoded SecretsBasic Auth Credentials In URL
- JavaScript / TypeScript - Hardcoded SecretsDB Connection String With Credentials
- JavaScript / TypeScript - Hardcoded SecretsHardcoded Credential String
- JavaScript / TypeScript - Hardcoded SecretsHardcoded Crypto Key Or IV
- Python - Hardcoded SecretsBasic Auth Credentials In URL
- Python - Hardcoded SecretsDB Connection String Credentials