CVE-2026-25803: Bcrypt Hash With Hardcoded Password Literal
bcrypt.hash() / bcrypt.hashSync() is being called with a hardcoded string literal as the password argument. This embeds a known credential into the source code (CWE-798: Use of Hard-coded Credentials). Even if the resulting bcrypt hash is stored in a database, the cleartext password is publicly visible in the repository, so any attacker can authenticate with
TSgreprules fetch cve-2026-25803-bcrypt-hash-with-hardcoded-password-literal --engine opengrepDescription
bcrypt.hash() / bcrypt.hashSync() is being called with a hardcoded string literal as the password argument. This embeds a known credential into the source code (CWE-798: Use of Hard-coded Credentials). Even if the resulting bcrypt hash is stored in a database, the cleartext password is publicly visible in the repository, so any attacker can authenticate with
Community feedback
0 rule-level signals from signed-in users.
- Useful reports
- 0
- Context false positives
- 0
- Metadata suggestions
- 0
Contextual precision
Aggregated from approved scan feedback. False-positive reports describe observed scan contexts, not a global rule verdict.
- Findings observed
- 0
- Projects
- 0
- Reporters
- 0
Precision details are collecting more signed-in reports before verdict counts or ratios are emphasized.
No approved finding verdicts yet.
No scan diagnostics reported yet.