Medium · CVSS 6.8CVE-2026-14867

Insecure password storage in User directoryCVE-2026-14867

Answer in brief

CVE-2026-14867 records a Medium severity (CVSS 6.8) vulnerability in Insecure password storage in User directory. The current sources do not mark it as known exploited. The current feed maps arcinfo/PcVue (generic), arcinfo/PcVue (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Jul 7, 2026Updated Oct 25, 2026Source checked Nov 3, 2026First seen by HOL Jul 7, 2026Material review Oct 25, 2026

Upstream Advisory

Key facts

Risk: Medium · CVSS 6.8
Exploitation: Not marked as known exploited
Affected software: 3 mapped packages or products
Fix availability: Available

Why this deserves its current priority

CVSS is 6.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps arcinfo/PcVue (generic), arcinfo/PcVue (generic). Check affected ranges and fixed versions before updating.

Affected products and reported versions
Product	Affected versions	Fixed versions
cpe:2.3:a:arcinfo:pcvue::::::::	Not reported	Not reported

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
arcinfo/PcVuegeneric	>=0 <17.0.0	17.0.0
arcinfo/PcVuegeneric	*	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for arcinfo/PcVue, arcinfo/PcVue.
Review the reported fix. Source-reported 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 PcVue Initial Release 17.0.0 or later In a patched release, it will no longer be possible to load User directory from earlier versions. Existing projects designed with an earlier version require explicit migration using the ProjectUtility CLI tool. Instructions are provided in the product documentation ( Project Utility CLI reference https://www.pcvue.com/ProductHelp/PcVue/en/Content/Deployment/tools/project-utility-cli.php ). To verify that the patch is applied correctly, you must check that the File version property of the file ./bin/sv32.exe matches release 17.0.0 (17.0.0902.3726) or later, and ensure that any earlier release is no longer used. Available patches: Patch provided in: * PcVue 17.0.0 (17.0.0902.3726)

Evidence timeline and material changes

Published upstream
Jul 7, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Oct 25, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Jul 7, 2026

Sources and claim methodology

Source referencepcvue.com

Upstream source description

Credentials of built-in users are insecurely stored in the User directory of PcVue projects, all versions prior to 17.0.0. A local attacker could retrieve users’ credentials. Active Directory accounts are not affected by this vulnerability.

Quoted source text, attributed separately from HOL analysis.

Affected scope and exposure questions

The current feed maps arcinfo/PcVue (generic), arcinfo/PcVue (generic). Check affected ranges and fixed versions before updating.

Affected products and reported versions
Product	Affected versions	Fixed versions
cpe:2.3:a:arcinfo:pcvue::::::::	Not reported	Not reported

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
arcinfo/PcVuegeneric	>=0 <17.0.0	17.0.0
arcinfo/PcVuegeneric	*	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for arcinfo/PcVue, arcinfo/PcVue.

Review the reported fix. Source-reported 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 PcVue Initial Release 17.0.0 or later In a patched release, it will no longer be possible to load User directory from earlier versions. Existing projects designed with an earlier version require explicit migration using the ProjectUtility CLI tool. Instructions are provided in the product documentation ( Project Utility CLI reference https://www.pcvue.com/ProductHelp/PcVue/en/Content/Deployment/tools/project-utility-cli.php ). To verify that the patch is applied correctly, you must check that the File version property of the file ./bin/sv32.exe matches release 17.0.0 (17.0.0902.3726) or later, and ensure that any earlier release is no longer used. Available patches: Patch provided in: * PcVue 17.0.0 (17.0.0902.3726)

Sources and claim methodology

Upstream source description

Quoted source text, attributed separately from HOL analysis.