CVE-2026-87850 json
Session Token Exposure via URL Query String in Axence nVision
published 37m ago modified 37m ago
- cvss
- 6.3
- version 4.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no EPSS score yet
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Axence nVision 18
Is CVE-2026-87850 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 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 |
Affected products
- Axence nVision
Classification
- Weakness
-
- CWE-598 Use of HTTP Request With Sensitive Query String
References
-
cert.pl
/posts/2026/11/CVE-2026-87850
third-party-advisory
-
axence.net
/pl/nvision
product
Sources
- CVE List CVE-2026-87850
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.