Quick answers
- Is CVE-2026-88273 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-88273 being exploited in the wild.
- How severe is CVE-2026-88273?
- High severity, with a CVSS score of 7.2, published 10 September 2026.
- Which products and versions are affected?
- Geovision Gv-Lpc2211 V1.13.
- Is there a fix for CVE-2026-88273?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-88273 attacked?
- It is attacked with local access, in a network appliance.
- Am I affected by CVE-2026-88273?
- Check whether you run Geovision Gv-Lpc2211 at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
This vulnerability is a command injection flaw in the PPPoE configuration module of GeoVision GV-LPC2211 V1.13. The vulnerability arises because the PPPoE username input is improperly sanitized before being incorporated into a shell configuration assignment and sourced for execution. An authenticated administrator can inject shell metacharacters (such as backticks or command substitution syntax) into the PPPoE username field to break out of the intended variable assignment context and execute arbitrary commands as root. No network-level authentication bypass is required—the attacker must have administrative access to the device. A successful exploit grants complete system compromise with root-level command execution.
Affected products
- GeoVision GV-LPC2211 V1.13
Timeline
- 2026-09-10: disclosed