# CVE-2026-87850: Axence nVision user token exposed in GET query string (CWE-598)

> CERT Polska reports that Axence nVision sends the user's token in the query parameters of GET requests. An attacker who obtains a valid token can access the victim's account and act on their behalf. Versions before 18 are affected; fixed in version 18.

- **Published:** 2026-11-19T06:49:41Z
- **Last reviewed:** 2026-11-19T06:49:41Z
- **Canonical:** https://intel.threadlinqs.com/threat/TL-2026-6425
- **Card image:** https://intel.threadlinqs.com/og/threat/TL-2026-6425.png
- **ID:** TL-2026-6425
- **Severity:** MEDIUM (CVSS 6.3)
- **Category:** VULNERABILITY
- **Status:** PATCHED
- **Detections:** 9 (1 shown free below) · **IOCs:** 8 (2 shown free below)
- **CVEs:** CVE-2026-87850

## Description

CVE-2026-87850 is a sensitive-information-exposure weakness in Axence nVision, a network and IT infrastructure monitoring product. Per the CERT Polska advisory and the NVD record, nVision sends the user's authentication token via the query parameters of GET requests (CWE-598, Use of GET Request Method With Sensitive Query Strings).

Tokens placed in URLs are commonly recorded in places such as browser history, proxy and web server logs and Referer headers, so they are exposed more widely than tokens carried in headers or request bodies. The sources do not describe how an attacker would obtain a token; they state only that an attacker who obtains a valid token can access the victim's account and act on the victim's behalf.

All nVision versions before 18 are affected and the issue is fixed in version 18. The vulnerability was reported to CERT Polska by Pawel Sledz and disclosed through CERT Polska's coordinated vulnerability disclosure process on 2026-11-18. CERT Polska (cvd@cert.pl) scored it CVSS 4.0 6.3 (MEDIUM). CISA's SSVC assessment recorded exploitation: none, automatable: no, technical impact: partial. No public proof-of-concept, in-the-wild exploitation, threat actor attribution or indicators of compromise are stated in any source.

## MITRE ATT&CK

- T1528 Steal Application Access Token
- T1550.001 Use Alternate Authentication Material: Application Access Token
- T1078 Valid Accounts
- T1078 Valid Accounts
- T1552 Unsecured Credentials

## Free detection (Splunk SPL, Microsoft KQL, Sigma)

**Axence nVision Token in GET Query String (CVE-2026-87850)** (`TL-2026-6425-SPL-001`)

Flags nVision requests that carry a user authentication token in the GET query string (CWE-598, CVE-2026-87850, nVision before 18). Such URLs land in proxy/web logs, browser history and Referer headers where an attacker can harvest the token (T1552, T1552.001, T1528). Output shows a hash of the token only.

- **Languages:** Splunk SPL, Microsoft KQL, Sigma
- **ATT&CK:** T1552, T1552.001, T1528
- **Data sources:** iis_w3c_logs (index=web sourcetype=ms:iis:auto / Sentinel W3CIISLog), web_proxy_logs (sourcetype=squid:access / access_combined / Sentinel CommonSecurityLog)
- **Severity:** medium
- **Confidence:** medium

### Splunk SPL

```spl
index=web (sourcetype="ms:iis:auto" OR sourcetype="access_combined" OR sourcetype="squid:access") (nvision OR axence) earliest=-24h
| eval qs=mvindex(split(coalesce(cs_uri_query, uri_query, url, uri),"?"),-1), src=coalesce(c_ip, clientip, src_ip, src), ua=coalesce(cs_User_Agent, http_user_agent, useragent), st=coalesce(status, sc_status), port=coalesce(s_port, dest_port), fullurl=coalesce(url, uri)
| eval pairs=split(qs,"&")
| eval tokpair=mvindex(mvfilter(match(pairs,"(?i)^(token|access_token|auth_token|authtoken|session_token|sessionid|sid)=.{8,}")),0)
| where isnotnull(tokpair)
| eval tok_param=mvindex(split(tokpair,"="),0), tok_hash=substr(md5(mvindex(split(tokpair,"="),1)),1,12)
| stats count min(_time) as first_seen max(_time) as last_seen values(tok_param) as token_param dc(tok_hash) as distinct_tokens values(src) as clients by host
| convert ctime(first_seen) ctime(last_seen)
```

### Microsoft KQL

```kql
let TokenRe = @"(?i)(?:^|[?&])(token|access_token|auth_token|authtoken|session_token|sessionid|sid)=([^&\s]{8,})";
let NvRequests = union
    (W3CIISLog
    | where TimeGenerated > ago(24h)
    | where csHost has "nvision" or sSiteName has "nvision" or csUriStem has "nvision"
    | project TimeGenerated, SrcIp = cIP, UserAgent = csUserAgent, Query = csUriQuery, Path = csUriStem, Status = tostring(scStatus), Port = tostring(sPort)),
    (CommonSecurityLog
    | where TimeGenerated > ago(24h)
    | where RequestURL has "nvision"
    | project TimeGenerated, SrcIp = SourceIP, UserAgent = RequestClientApplication, Query = RequestURL, Path = tostring(split(RequestURL, "?")[0]), Status = "", Port = tostring(DestinationPort));
NvRequests
| where Query matches regex TokenRe
| extend TokenParam = extract(TokenRe, 1, Query), TokenHash = substring(hash_sha256(extract(TokenRe, 2, Query)), 0, 12)
| summarize Requests = count(), FirstSeen = min(TimeGenerated), LastSeen = max(TimeGenerated), DistinctTokens = dcount(TokenHash), Clients = make_set(SrcIp, 20) by TokenParam
```

### Sigma

```yaml
title: Axence nVision User Token in GET Query String
id: 5b0c1a64-3e1f-4c7e-9a52-6d2f8e1b7a01
name: nvision_token_in_query
status: experimental
description: Detects nVision requests carrying an authentication token in the URL query string (CVE-2026-87850, CWE-598).
references:
    - https://cert.pl/en/posts/2026/11/CVE-2026-87850/
    - https://www.cve.org/CVERecord?id=CVE-2026-87850
author: Threadlinqs Team
date: 2026-11-19
tags:
    - attack.credential_access
    - attack.t1528
    - attack.t1552
    - attack.t1552.001
    - cve.2026.87850
logsource:
    category: webserver
detection:
    selection:
        cs-host|contains: 'nvision'
        c-uri-query|re: '(?i)(^|[?&])(token|access_token|auth_token|authtoken|session_token|sessionid|sid)=[^&\s]{8,}'
    condition: selection
falsepositives:
    - Legitimate nVision console users on versions before 18 (the token is carried in the URL by design)
    - Security scanners and monitoring probes hitting nVision
level: medium

```

**Known false positives:**

- Legitimate nVision users on versions before 18, whose token is always carried in the URL
- Vulnerability scanners and uptime monitors that request nVision pages with a service token

**Tuning notes:** The research does not name the exact nVision token parameter; the regex covers common names (token, access_token, auth_token, sessionid, sid). Point the host/site filter at your real nVision host and add the real parameter name once confirmed in your own logs. Token values are hashed, never output. Upgrading to nVision 18 and rotating tokens removes the baseline noise.

### 8 more detection rules (Splunk SPL, Microsoft KQL, Sigma), unlock with TL Creds

- Axence nVision Token Leaked via Referer to Non-nVision Host (locked: unlock with TL Creds)
- Axence nVision Single Client Presenting Many Distinct Tokens (locked: unlock with TL Creds)
- Axence nVision Token Request from Scripted HTTP Client (locked: unlock with TL Creds)
- Axence nVision Token in Cleartext HTTP URL (locked: unlock with TL Creds)
- Axence nVision Repeated Rejected Token Requests from One Client (locked: unlock with TL Creds)
- Axence nVision Token-Bearing Client Enumerating Many Distinct Endpoints (locked: unlock with TL Creds)
- Axence nVision Token-Bearing Request from Non-Internal Client (locked: unlock with TL Creds)
- Axence nVision Same Token Used from Multiple Source IPs (locked: unlock with TL Creds)

Sign up free to unlock the detection rules: https://threadlinqs.com/?modal=signup

## Sample indicators (2 of 8)

Defanged, TLP:CLEAR.

- URL: `hxxps://cert[.]pl/en/posts/2026/11/CVE-2026-87850/`
- URL: `hxxps://www[.]cve[.]org/CVERecord?id=CVE-2026-87850`

Full set of 8 indicators unlocks with TL Creds: https://threadlinqs.com/tl-creds

## Sources

- [Vulnerability in Axence nVision software (CERT Polska)](https://cert.pl/en/posts/2026/11/CVE-2026-87850/)
- [NVD API record for CVE-2026-87850](https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-87850)
- [CVE Record CVE-2026-87850](https://www.cve.org/CVERecord?id=CVE-2026-87850)
- [Axence nVision product page](https://axence.net/pl/nvision)
- [CERT Polska coordinated vulnerability disclosure policy](https://cert.pl/en/cvd/)

## Full data

The other 8 detection rules (Splunk SPL / Microsoft KQL / Sigma) unlock with TL Creds; a free account includes daily creds: https://threadlinqs.com/?modal=signup
Indicator values unlock with TL Creds, at a lower price on Red and Purple; AI agents can query rules and IOCs through the Threadlinqs MCP server (Purple): https://intel.threadlinqs.com/mcp

Canonical: https://intel.threadlinqs.com/threat/TL-2026-6425
