# CVE-2026-53986: Girafit Camera App 1.9.1 Hardcoded TURN Credentials Disclosure


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 21 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** GHSA-vwwq-ggwp-4879

## What is CVE-2026-53986?

CVE-2026-53986 is a medium-severity vulnerability in Girafit camera app, published on 21 Oct 2026. 

### Official description

Girafit camera app (Android and iOS) version 1.9.1 and earlier, and Girafit camera devices, contain a hardcoded credentials vulnerability that allows attackers to obtain the shared TURN relay username by decompiling the app or intercepting unencrypted network traffic during live view registration. Attackers can extract the static TURN username and session token, which are identical across all installs and not tied to any user or device, potentially enabling tracking, impersonation, or further exploitation if combined with the TURN relay password.

Weakness: CWE-798 (Use of Hard-coded Credentials), CWE-319 (Cleartext Transmission of Sensitive Information)

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


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

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

## Is CVE-2026-53986 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-53986 is a medium-severity vulnerability in Girafit camera app, published on 21 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-53986 exists.

Affected product: Girafit camera app. 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-53986/ (Markdown: https://insights.sbomify.com/CVE-2026-53986/index.md)
```

## Sources

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

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