CVE-2026-105147
Deferred Deferred - Pending Action

Hard-Coded Credentials in SciPhi-AI R2R

Publication date: 2026-10-04

Last updated on: 2026-10-04

Assigner: VulDB

Description
A vulnerability was determined in SciPhi-AI R2R up to 3.6.6. This affects an unknown part of the component JWT Secret Handler. This manipulation of the argument DEFAULT_BCRYPT_SECRET_KEY/DEFAULT_NACL_SECRET_KEY causes hard-coded credentials. The attack can be initiated remotely. The exploit has been publicly disclosed and may be utilized. The vendor was contacted early about this disclosure but did not respond in any way.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-04
Last Modified
2026-10-04
Generated
2026-10-04
AI Q&A
2026-10-04
EPSS Evaluated
N/A
NVD
CVE-2026-105147
EUVD
EUVD-2026-92093

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
sciphi-ai r2r to 3.6.6 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-798 The product contains hard-coded credentials, such as a password or cryptographic key.
CWE-259 The product contains a hard-coded password, which it uses for its own inbound authentication or for outbound communication to external components.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-105147 is a vulnerability in SciPhi-AI R2R versions up to 3.6.6 where hardcoded JWT secrets allow remote attackers to forge admin access tokens. The issue occurs because the system uses default secrets (DEFAULT_BCRYPT_SECRET_KEY/DEFAULT_NACL_SECRET_KEY) when no custom secret is provided, enabling unauthenticated API access.

Detection Guidance

Check R2R versions up to 3.6.6 for hardcoded JWT secrets in source code or Docker environment files. Search for the default secret 'wNFbczH3QhUVcPALwtWZCPi0lrDlGV3P1DPRVEQCPbM' in configuration files or environment variables. Verify if JWT tokens can be forged without authentication by inspecting API responses or logs for unauthorized access attempts.

Commands: grep -r 'wNFbczH3QhUVcPALwtWZCPi0lrDlGV3P1DPRVEQCPbM' /path/to/r2r/; docker inspect <container_name> | grep -i secret; curl -X POST http://<target>/api/login -H 'Authorization: Bearer <test_token>' to check for access bypass.

Impact Analysis

An attacker can exploit this to bypass authentication entirely, gaining full API access including user management and document operations. This allows unauthorized data access, modification, or deletion. The impact is severe as it persists even if admin passwords are changed or authentication is enforced.

Compliance Impact

This vulnerability likely violates compliance requirements for data protection (GDPR, HIPAA) due to unauthorized access risks. It undermines security controls, potentially leading to data breaches and non-compliance with access control and encryption standards.

Mitigation Strategies

Update R2R to the latest version beyond 3.6.6. Remove hardcoded secrets from source code and Docker files. Set a unique R2R_SECRET_KEY environment variable before starting the service. Rotate all JWT secrets and invalidate existing tokens. Ensure require_authentication is enforced in configurations.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-105147. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart