CVE-2026-108983

validatingZero is analyzing and reversing it now.

GHSA-4688-jpp9-vr89 ↗EUVD-2026-104030 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
GeoVision Inc. GV-ASManager 6.3.0
CWE-78 Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
ETK-2026-2027Zero's internal tracking ID, independent of the CVE number., permanent identifier
1h 13mrunning
patch analysiscurrent stage
timeline
0 = trigger signal
trigger signal (cve.org) +0dvalidating
0
+1d
+2d

description

GV-ASManager deployments using the GeoWebServer.exe web service may be vulnerable to command injection through its default network ports. An unauthenticated remote attacker may be able to execute commands if they can reach the exposed service.

Still under analysis: more detail becomes available as the pipeline runs.

mitigation

Restrict access to the GeoWebServer.exe default ports to trusted administrative networks and remove public exposure. No fixed version is recorded; apply a vendor-provided update when one becomes available.

check
building now
exploit
not yet
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
–
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.31%22nd percentile
agent run time
1h 13m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-19 00:51Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Run in progress: no artifact yet.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-19 00:51Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-108983

{
  "etk_id": "ETK-2026-2027",
  "cve_id": "CVE-2026-108983",
  "display_id": "CVE-2026-108983",
  "ghsa_id": "GHSA-4688-jpp9-vr89",
  "euvd_id": "EUVD-2026-104030",
  "status": "in_pipeline",
  "anchor_state": "anchored",
  "title": "Command injection in GeoVision GV-ASManager web server",
  "summary": "GV-ASManager deployments using the GeoWebServer.exe web service may be vulnerable to command injection through its default network ports. An unauthenticated remote attacker may be able to execute commands if they can reach the exposed service.",
  "mitigation": "Restrict access to the GeoWebServer.exe default ports to trusted administrative networks and remove public exposure. No fixed version is recorded; apply a vendor-provided update when one becomes available.",
  "vendor": "GeoVision Inc.",
  "product": "GV-ASManager",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "6.3.0"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "GV-ASManager",
      "purl": null
    }
  ],
  "cwes": [
    78
  ],
  "cvss_score": 9.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": 0.0031,
  "epss_percentile": 0.2286,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 74.97478251666666,
  "t0_at": "2026-10-19T00:51:53.770000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-19T00:51:53.770000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-19T00:51:53.770000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-108983"
    }
  }
}

published 2026-10-19 02:31Z
last change 2026-10-21 03:57Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.