LiveActive security incident?Get immediate response
CVE Record

CVE-2026-1694: Server configuration details in HTTP headers

HTTP headers are added by the default configuration of IIS and ASP.net, and are not removed at the deployment phase of the webservices used by the WebVue, WebScheduler, TouchVue and SnapVue features of PcVue in version 12.0.0 through 16.3.3 included. It unnecessarily exposes sensitive information about the server configuration.

LowCVSS 2.3Not KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

CVE-2026-1694 is an information exposure issue in PcVue web features. Default IIS and ASP.NET HTTP headers were left visible, disclosing server configuration details. This does not directly compromise data or availability, but it can help an attacker profile systems for future attacks.

Executive priority

Treat as a low-priority hardening issue unless the affected PcVue webservices are internet-exposed or protect critical operational environments. It should be addressed during normal maintenance and exposure reduction work, not as an emergency response.

Technical view

PcVue WebVue, WebScheduler, TouchVue, and SnapVue webservices in versions 12.0.0 through 16.3.3 include default IIS/ASP.NET HTTP headers that unnecessarily expose server configuration information. The issue is categorized as CWE-201 with CVSS 4.0 score 2.3 low severity.

Likely exposure

Organizations using affected PcVue web features may expose server metadata through HTTP responses, especially where those services are reachable over a network. Exposure depends on whether WebVue, WebScheduler, TouchVue, or SnapVue are deployed and accessible.

Exploitation context

No active exploitation is reported in the provided sources, and the CVE is not listed as KEV. The value to attackers is reconnaissance: disclosed server details may support targeting or chaining with separate vulnerabilities.

Researcher notes

Evidence is limited to the CVE record and vendor advisory reference. The issue is configuration information disclosure, not code execution. Avoid overstating impact; focus validation on affected features, versions, reachability, and exposed HTTP headers.

Mitigation direction

  • Review ARC Informatique/PcVue advisory SB2026-2 for official remediation guidance.
  • Inventory PcVue deployments and identify versions 12.0.0 through 16.3.3.
  • Determine whether WebVue, WebScheduler, TouchVue, or SnapVue webservices are enabled.
  • Reduce unnecessary network exposure to affected webservices where operationally feasible.
  • Remove unnecessary server-identifying headers only according to vendor-supported guidance.

Validation and detection

  • Confirm installed PcVue version and enabled web features.
  • Inspect HTTP responses from PcVue webservices for IIS or ASP.NET configuration headers.
  • Compare observed behavior against vendor advisory SB2026-2.
  • Document externally reachable instances separately from internal-only deployments.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-201: Information exposure and cloud metadata lookup

Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-1694 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Low
CVSS
2.3 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:P/VC:N/VI:N/VA:N/SC:L/SI:N/SA:N/AU:Y/R:U/RE:M/U:Clear

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
2.3CVSS 4.0LowCVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:P/VC:N/VI:N/VA:N/SC:L/SI:N/SA:N/AU:Y/R:U/RE:M/U:Clear——Primary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

2.3Low
CVSS 4.0 vector shape for CVE-2026-1694Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:P/VC:N/VI:N/VA:N/SC:L/SI:N/SA:N/AU:Y/R:U/RE:M/U:Clear

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
arcinfoPcVue16.0.0, 15.0.0, 12.0.0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-201 · source CWE mapping

Insertion of Sensitive Information Into Sent Data

Insertion of Sensitive Information Into Sent Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.