High severityGoHardcoded SecretsHIGH confidence
Hardcoded JWT Signing Key
A JWT is signed or verified with a hardcoded HMAC key literal (CWE-798/CWE-321).
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 token.SignedString([]byte("my-hardcoded-hmac-secret"))Passes - the safe pattern
return token.SignedString(secretFromEnv)Why it matters & how to fix it
A JWT is signed or verified with a hardcoded HMAC key literal (CWE-798/CWE-321). Anyone who reads the source or binary can forge or verify arbitrary tokens. Load the signing secret from an environment variable or secrets manager at runtime, use a high-entropy key, and rotate any secret that was committed.
References
Rule ID integsec-go-hardcoded-jwt-signing-key - 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