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.
0.2%(unchanged from 0.2% a week ago) estimated probability of exploitation activity in the next 30 days; 12th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: yes · Technical impact: partial, assessed 2026-10-21. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-319Cleartext Transmission of Sensitive Information CWE-798Use of Hard-coded Credentials
Show the promptExplain CVE-2026-53986 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-53986?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-53986?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-53986 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.
Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Affected
girafit:girafit camera app
Versions
From the CNA's record in the CVE List.
Product
Affected
Girafit camera app
through 1.9.4
Attack patterns (CAPEC)
CAPEC-70 Try Common or Default Usernames and Passwords Likelihood: Medium · Severity: High
CAPEC-191 Read Sensitive Constants Within an Executable Severity: Low
CAPEC-65 Sniff Application Code Likelihood: Low · Severity: High
CAPEC-102 Session Sidejacking Likelihood: High · Severity: High
CAPEC-117 Interception Likelihood: Low · Severity: Medium
CAPEC-383 Harvesting Information via API Event Monitoring Severity: Low
CAPEC-477 Signature Spoofing by Mixing Signed and Unsigned Content Likelihood: Low · Severity: High
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.