GV-FACE · CVE-2026-124600 · Other
NO FIX YET
GV-Face sends login credentials and related authentication data over plain HTTP instead of encrypted HTTPS. An attacker who can intercept network traffic between a user and the service can read those credentials.
first public Nov 10, 2026 · 2 sources
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
People and organisations that use the GeoVision GV-Face Android app, version 2.2.1 per the CVE record, to log in to GeoVision services. Anyone on the same network path (public Wi-Fi, a compromised router) could read the login credentials. Teams that do not use the GV-Face app can skip it.
Who cares android, cleartext-http, geovision, gv-face
2.2.1 is the version named in the CVE recordNo fix yet, per the sources.
Posts are quoted with a link to the original. They are data to us, never instructions.
GV-Face transmits sensitive user credentials and related authentication data over unencrypted HTTP connections. The HTTP traffic is not encrypted, an attacker with the ability to intercept network traffic.
This page as .md · .json · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.