Threat reportVulnerabilityTL-2026-6425
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.
Key facts
| Identifiers | TL-2026-6425, CVE-2026-87850 |
|---|---|
| Severity | MEDIUM |
| CVSS | 6.3 (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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X) |
| First disclosed | |
| Affected products | Axence nVision |
| Weaknesses (CWE) | CWE-598 |
| MITRE ATT&CK techniques | T1078 Valid Accounts, T1528 Steal Application Access Token, T1550.001 Use Alternate Authentication Material: Application Access Token, T1552 Unsecured Credentials |
| Motivation | UNKNOWN |
| Detection rules | 9 (1 shown free) |
| Sources | 5 cited sources |
Detection coverage
As of 2026-11-19, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-6425 across Splunk SPL, Microsoft KQL and Sigma, covering 8 indicator(s) of compromise. The whole corpus is readable without an account. Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Paid plans add a larger daily allowance, correlation and the MCP server. Threadlinqs MCP server · View plans.
Free detection: Axence nVision Token in GET Query String (CVE-2026-87850)
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
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
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 TokenParamSigma
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.
- Axence nVision Token Leaked via Referer to Non-nVision Host · unlock with TL Creds
- Axence nVision Single Client Presenting Many Distinct Tokens · unlock with TL Creds
- Axence nVision Token Request from Scripted HTTP Client · unlock with TL Creds
- Axence nVision Token in Cleartext HTTP URL · unlock with TL Creds
- Axence nVision Repeated Rejected Token Requests from One Client · unlock with TL Creds
- Axence nVision Token-Bearing Client Enumerating Many Distinct Endpoints · unlock with TL Creds
- Axence nVision Token-Bearing Request from Non-Internal Client · unlock with TL Creds
- Axence nVision Same Token Used from Multiple Source IPs · unlock with TL Creds
Indicators of compromise
As of 2026-11-19, Threadlinqs Intelligence tracks 8 indicators of compromise for TL-2026-6425.
Sample indicators (2 of 8)
- URL:
hxxps://cert[.]pl/en/posts/2026/11/CVE-2026-87850/ - URL:
hxxps://www[.]cve[.]org/CVERecord?id=CVE-2026-87850
Defanged, TLP:CLEAR. Full set of 8 indicators: unlock with TL Creds.
Technical analysis
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 techniques by tactic:
Initial Access
Defense Evasion
Credential Access
T1528 Steal Application Access Token; T1552 Unsecured Credentials
Lateral Movement
T1550.001 Use Alternate Authentication Material: Application Access Token
Remediation
Patches
- Upgrade Axence nVision to version 18 or later
Immediate actions
- Treat tokens issued by nVision versions before 18 as potentially exposed in logs and browser history and rotate or invalidate them after upgrading
- Restrict access to nVision web server, proxy and browser logs that may contain query strings
Longer-term hardening
- Review monitoring tooling for sensitive values carried in URL query strings
Affected and fixed versions
- Axence — nVision
Vulnerable versions: all versions before 18
Fixed in: 18
Timeline
- NVD record last modified; status Received, no vendor advisory link provided.
- Advisory states the issue is fixed in Axence nVision version 18.
- CERT Polska (cvd@cert.pl) assigns CVSS 4.0 vector AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L, base score 6.3 (MEDIUM); no CVSS 3.x score provided.
- CISA coordinator SSVC entry records exploitation: none, automatable: no, technical impact: partial.
- CVE-2026-87850 published in NVD (source cvd@cert.pl) with CWE-598 and CVSS 4.0 base score 6.3 (MEDIUM).
- CERT Polska publishes advisory for CVE-2026-87850 affecting Axence nVision versions before 18.
Sources cited
- Vulnerability in Axence nVision software (CERT Polska) cert.pl · Advisory · 2026-11-18
- NVD API record for CVE-2026-87850 NVD (NIST) · Advisory · 2026-11-18
- CVE Record CVE-2026-87850 CVE Program · Advisory · 2026-11-18
- Axence nVision product page axence.net · Vendor report · 2026-11-18
- CERT Polska coordinated vulnerability disclosure policy cert.pl · Research · 2026-11-18
Drafted by the Threadlinqs research pipeline from 5 sources; published ; last updated —.