SSVR service crash via fragment reassembly overflow
Published Sep 10, 2026 · Updated Sep 10, 2026
Stack-based buffer overflow in GeoVision GV-LPC2011/LPC2211 1.13 and earlier allows remote authenticated users to crash SSVR via fragment reassembly. The reassembly path writes fragment data beyond a fixed-size stack buffer; GeoVision has not disclosed the affected function or bounds check. Valid SSVR credentials and network reachability are required, and the reported consequence is an SSVR service interruption rather than data disclosure or modification.
Summary
What happened
Stack-based buffer overflow in GeoVision GV-LPC2011/LPC2211 1.13 and earlier allows remote authenticated users to crash SSVR via fragment reassembly. The reassembly path writes fragment data beyond a fixed-size stack buffer; GeoVision has not disclosed the affected function or bounds check. Valid SSVR credentials and network reachability are required, and the reported consequence is an SSVR service interruption rather than data disclosure or modification.
The record
- CVE
- CVE-2026-88268
- Published
- Sep 10, 2026
- Updated
- Sep 10, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-121, CAPEC-100, T1499.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 10, 2026CVE publishedPublication date reported by the CVE source.
- Sep 10, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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