Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-112160Unauthorized Modification of User Account Security Settings

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.

Timeline

  1. ID reserved

    By arcinfo

  2. · 30 days later

    Published

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-112160, by who scored it
Scored byCVSSScoreVector
arcinfoCNA (assigner)4.0Low2.0CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
NVDNVD · Received4.0Low2.0CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:N/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
EPSS (exploitation in 30 days)
0.13% · top 97% of all CVEs (19 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Low 2.0.

Affected products

What to do

Solution: Harden the configuration Who should apply this recommendation: All users To reduce the risk of exploitation, ARC Informatique strongly recommends implementing the following defensive measures: * Minimize network exposure for all control system devices and/or systems, and ensure they are not accessible from insecure networks. * Locate control system networks and remote devices behind firewalls and isolate them from business networks. * When remote access is required, use secure methods, such as Virtual Private Networks (VPNs), recognizing VPNs may have vulnerabilities and should be updated to the most current version available. Also recognize VPN is only as secure as its connected devices. Additional deployment guidance and recommended practices are available in the product documentation ( Hardening Guide https://www.pcvue.com/ProductHelp/PcVue/en/Content/Deployment/hardening-guide/overview.php ). Update PcVue Who should apply this recommendation: All users using the affected component Apply the corrective update by installing a fixed PcVue version or later To verify that the patch is applied correctly, you must check that the File version property of the file ./bin/sv32.exe matches the patched release or later, and ensure that any earlier release is no longer used. Available patches: Patch provided in: * PcVue 17.1.0 (17.1.0902.4079)

Exploitation: No POC available.

Exploitation: Not known to be exploited

References

References1

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-112160 badge
[![CVE-2026-112160](https://cveledger.app/badge/CVE-2026-112160.svg)](https://cveledger.app/cve/CVE-2026-112160)

Record last updated .