PatchSiren cyber security CVE debrief
CVE-2026-105147 SciPhi-AI CVE debrief
CVE-2026-105147 is a vulnerability in SciPhi-AI R2R up to 3.6.6, affecting the JWT Secret Handler component. The vulnerability causes hard-coded credentials due to manipulation of the DEFAULT_BCRYPT_SECRET_KEY/DEFAULT_NACL_SECRET_KEY argument. The attack can be initiated remotely, and the exploit has been publicly disclosed. The vendor was contacted but did not respond.
- Vendor
- SciPhi-AI
- Product
- R2R
- CVSS
- MEDIUM 5.5
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-10-04
- Original CVE updated
- 2026-10-04
- Advisory published
- 2026-10-04
- Advisory updated
- 2026-10-04
Who should care
Defenders responsible for SciPhi-AI R2R deployments, especially those using versions up to 3.6.6, should assess their exposure and prioritize verification and potential remediation.
Why it matters
CVE-2026-105147 is a medium-severity vulnerability in SciPhi-AI R2R that allows for hardcoded credentials, enabling remote attacks. Defenders should prioritize verification, assessment, and potential remediation to prevent credential misuse.
- Verification of SciPhi-AI R2R version and potential exposure to hardcoded credentials
- Assessment of remote attack feasibility and potential impact
- Monitoring for exploit usage and potential credential misuse
- Prioritization of authentication and secret management compensating controls
Technical summary
The SciPhi-AI R2R up to 3.6.6 is vulnerable to hardcoded credentials due to improper handling of DEFAULT_BCRYPT_SECRET_KEY/DEFAULT_NACL_SECRET_KEY in the JWT Secret Handler component. This allows for remote attacks. Defenders should verify the presence of this vulnerability in their SciPhi-AI R2R deployments, especially if they are using versions up to 3.6.6, and assess the potential impact of hardcoded credentials. The CVE record and NVD entry provide details about the vulnerability, but the vendor did not respond to the disclosure.
Defensive priority
Defenders should prioritize verifying the presence of this vulnerability in their SciPhi-AI R2R deployments, especially if they are using versions up to 3.6.6, and assess the potential impact of hardcoded credentials.
Recommended defensive actions
- Verify SciPhi-AI R2R deployments for version 3.6.6 or earlier
- Assess potential impact of hardcoded credentials
- Monitor for exploit usage
- Consider compensating controls for authentication and secret management
- Review vendor guidance for patching or mitigation
- Conduct asset inventory to identify exposed systems
- Track exceptions and retest remediated assets
Evidence notes
The CVE record and NVD entry provide details about the vulnerability, but the vendor did not respond to the disclosure. The exploit has been publicly disclosed, but there is no information on its usage.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-105147 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-105147
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-105147 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-105147
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://gist.github.com/DReazer/6bc4f88053ec35f8358395bcc0d1a0bb
-
Source reference
Unverified legacy reference
URL: https://vuldb.com/cve/CVE-2026-105147
-
Source reference
Unverified legacy reference
URL: https://vuldb.com/submit/947748
-
Source reference
Unverified legacy reference
URL: https://vuldb.com/vuln/413372
-
Source reference
Unverified legacy reference
URL: https://vuldb.com/vuln/413372/cti
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.