CVE
PcVue authorization bypass in user account security settings
- Exploited
- No known exploitation
- Fix
- Fixed in 17.1.0
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 17.1.0.
Summary
PcVue, from arcinfo, has a flaw that lets a privileged local user change user account security settings, such as password policies, without authorization. The attacker must already be logged in with low privileges and access the system locally.
Original description
In PcVue version 17.0.0 through 17.0.1 included, user account security settings could be modified. This could lead to unauthorized modification of password policies or other security-related account settings by privileged users. The update aligns user account management with the existing security-altering enforcement model and prevents unauthorized security configuration changes.
cve.now Index
- Exploitation0/40No signal
- Exposure?/25Unknown. No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity2/10CVSS 2.0
- No patch0/5No signal
What would change the score
- Would score about 57 if added to CISA KEV
- Would score about 52 if CISA's SSVC rates exploitation active
- Would score about 24 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 17.1.0.
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-112160 (Unauthorized Modification of User Account Security Settings), 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-112160 (entry last updated 2026-11-18):
Affected:
- arcinfo PcVue: from 17.0.0, fixed in 17.1.0
Fixed versions: 17.1.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-112160 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-112160 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://www.pcvue.com/security/#SB2026-9
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-112160
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-112160"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- arcinfo PcVue
From 17.0.0 · fixed in 17.1.0
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | pcvue.com · security#SB2026-9 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-112160 |
| Record | NVD · CVE-2026-112160 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-112160
Is CVE-2026-112160 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-112160?
PcVue: from 17.0.0 before 17.1.0.Source: cve.now feed data
How do I fix CVE-2026-112160?
Upgrade to a fixed version: 17.1.0.Source: cve.now feed data