# CVE-2026-105147: SciPhi-AI R2R JWT Secret hard-coded credentials

> Hard-coded JWT secrets in SciPhi-AI R2R allow remote attackers to bypass authentication and potentially take over accounts.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Oct 2026
- **Updated:** 5 Oct 2026
- **Also known as:** GHSA-hw45-xf9v-jg9c

## What is CVE-2026-105147?

CVE-2026-105147 is a medium-severity vulnerability in SciPhi-AI R2R, published on 4 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-798 (Use of Hard-coded Credentials), CWE-259 (Use of Hard-coded Password)

## Which versions are affected by CVE-2026-105147?


## How do I fix CVE-2026-105147?

No fix has been published for CVE-2026-105147 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-105147 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-105147 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-105147 and fix it if it is affected.

What it is: CVE-2026-105147 is a medium-severity vulnerability in SciPhi-AI R2R, published on 4 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-105147 exists.

Affected product: SciPhi-AI R2R. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-105147/ (Markdown: https://insights.sbomify.com/CVE-2026-105147/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-105147
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-105147
- OSV: https://osv.dev/vulnerability/CVE-2026-105147

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-105147/
Summaries are generated and may contain mistakes; the official description above is the record.