Skip to main content
VulnerabilityPublished

CVE-2026-87850: Axence nVision · Use of HTTP Request With Sensitive Query String

Affects Axence nVisionSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.3 Medium : upgrade to 18 when convenient.

Data as of 18 Nov 2026, 11:04 UTC

CVSS 4.0 base score
6.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (CERT-PL)CVSS 4.06.3
Patch
Available – fixed in 18
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Upgrade Axence nVision to 18.

Affected software

ProductAffectedFixed in
AxencenVisionAffected
  • <18
Fixed in
  • 18

AI-suggested

Upgrade Axence nVision to version 18 or later, where this vulnerability has been fixed. No other mitigation is necessary as the vendor has provided an official fix.

Description

Axence nVision versions prior to 18 transmit user authentication tokens via HTTP GET request query parameters. This practice exposes tokens to interception or leakage through logs or network monitoring. An attacker who obtains a valid token can impersonate the user and perform unauthorized actions. The vulnerability is identified as CWE-598 and has a CVSS 4.0 base score of 6.3 (medium severity). The issue was fixed in version 18.

References

Community reviews

Loading reviews…