HTTPS decryption and spoofing via static TLS key
Published Aug 4, 2026 · Updated Aug 4, 2026
Hard-coded key exposure in GeoVision GV-AS1620 2.07 allows remote attackers to decrypt HTTPS traffic and impersonate the controller. The Lighttpd TLS endpoint uses an RSA private key embedded unchanged in the firmware instead of generating a device-specific secret. Remote attackers who recover the embedded key can decrypt captured HTTPS sessions and spoof the controller; service interruption is not reported.
Summary
What happened
Hard-coded key exposure in GeoVision GV-AS1620 2.07 allows remote attackers to decrypt HTTPS traffic and impersonate the controller. The Lighttpd TLS endpoint uses an RSA private key embedded unchanged in the firmware instead of generating a device-specific secret. Remote attackers who recover the embedded key can decrypt captured HTTPS sessions and spoof the controller; service interruption is not reported.
The record
- CVE
- CVE-2026-18753
- Published
- Aug 4, 2026
- Updated
- Aug 4, 2026
- Vendor
- GeoVision
- Product
- GV-AS1620
- Classifications
- CWE-321, CAPEC-633, T1557
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 4, 2026CVE publishedPublication date reported by the CVE source.
- Aug 4, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=V2.07
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo