# CVE-2026-75960: Insufficiently Protected Credentials in Rently Smart Home

> Attackers can retrieve master PINs to override user permissions in Rently Smart Home systems, requiring an upgrade to secure credentials.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Aug 2026
- **Updated:** 26 Aug 2026
- **Also known as:** GHSA-jfpj-vc23-8v7g

## What is CVE-2026-75960?

CVE-2026-75960 is a high-severity vulnerability in Rently Smart Home, published on 26 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Rently Smart Home versions 20.1.0 and prior are vulnerable to an Insufficiently Protected Credentials vulnerability. This could allow an attacker to retrieve pins including the Master Pin, overriding standard user permissions.

Weakness: CWE-522 (Insufficiently Protected Credentials)

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


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

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

## Is CVE-2026-75960 being exploited?

There is no known exploitation of CVE-2026-75960 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-75960 is a high-severity vulnerability in Rently Smart Home, published on 26 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-75960 in the wild and no public exploit code.

Affected product: Rently Smart Home. 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-75960/ (Markdown: https://insights.sbomify.com/CVE-2026-75960/index.md)
```

## Sources

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

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