CVE
Axence nVision session token exposure in URL query strings
- Exploited
- No known exploitation
- Fix
- Fixed in 18
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 18.
Summary
Axence nVision sends a user's session token in the URL query string of GET requests, where it can be exposed. An attacker who network-accessible, without logging in, obtains a valid token could take over the victim's account and act on their behalf.
Original description
nVision sends user's token via query parameters of GET requests. An attacker who obtains valid token can gain access to the victim's account and perform actions on their behalf.
This issue was fixed in version 18.
cve.now Index
- Exploitation0/40No signal
- Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity6.3/10CVSS 6.3
- No patch0/5No signal
What would change the score
- Would score about 68 if added to CISA KEV
- Would score about 63 if CISA's SSVC rates exploitation active
- Would score about 28 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 18.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-87850 (Session Token Exposure via URL Query String in Axence nVision), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-87850 (entry last updated 2026-11-18):
Affected:
- Axence nVision: fixed in 18
Fixed versions: 18.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-87850 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-87850 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://cert.pl/posts/2026/11/CVE-2026-87850
- https://axence.net/pl/nvision
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-87850
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-87850"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Axence nVision
fixed in 18
Evidence 4
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Link | axence.net · pl/nvision |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-87850 |
| Record | NVD · CVE-2026-87850 |
| Other links 1 | |
| Link | cert.pl · posts/2026/11/CVE-2026-87850 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-87850
Is CVE-2026-87850 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-87850?
nVision: before 18.Source: cve.now feed data
How do I fix CVE-2026-87850?
Upgrade to a fixed version: 18.Source: cve.now feed data