Cyber Resilience

CVE-2026-1697

Arcinfo Pcvue 12.0.0 – 15.2.13

Published
26 February 2026
Modified
09 July 2026
Patch / advisory
CVSS Score v4 5.3
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/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:Y/R:U/V:X/RE:M/U:Clear
EPSS Score 0.0012 2th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2026-1697 is a medium-severity Sensitive Cookie in HTTPS Session Without 'Secure' Attribute (CWE-614) vulnerability in Arcinfo Pcvue. Its CVSS base score is 5.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Steal Web Session Cookie (T1539); ranked at the 2th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SC-23 (Session Authenticity) and SC-8 (Transmission Confidentiality and Integrity) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

The Secure and SameSite attribute are missing in the GraphicalData web services and WebClient web app of PcVue in version 12.0.0 through 16.3.3 included.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

T1539 Steal Web Session Cookie Credential Access
An adversary may steal web application or service session cookies and use them to gain access to web applications or Internet services as an authenticated user without needing credentials.
T1550.004 Web Session Cookie Lateral Movement
Adversaries can use stolen session cookies to authenticate to web applications and services.
Why these techniques?

Missing Secure/SameSite cookie attributes directly facilitate web session cookie theft (T1539) and subsequent use as alternate auth material (T1550.004).

Confidence: HIGH · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2026-1695Same product: Arcinfo Pcvue
CVE-2026-14868Same product: Arcinfo Pcvue
CVE-2026-1696Same product: Arcinfo Pcvue
CVE-2026-1692Same product: Arcinfo Pcvue
CVE-2026-1694Same product: Arcinfo Pcvue
CVE-2026-1693Same product: Arcinfo Pcvue
CVE-2026-1698Same product: Arcinfo Pcvue
CVE-2026-41017Shared CWE-614
CVE-2025-8037Shared CWE-614
CVE-2026-43828Shared CWE-614

Affected Assets

arcinfo
pcvue
12.0.0 — 15.2.13 · 16.0.0 — 16.3.4

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • SC-8 Transmission Confidentiality and Integrity
  • SC-23 Session Authenticity
  • SI-2 Flaw Remediation
Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V3.3.2
  • V3.3.1

Mitigating Controls (NIST 800-53 r5) AI

prevent

Directly requires cryptographic protection of session cookies in transit, which the missing Secure attribute violates.

prevent

Enforces mechanisms that protect session authenticity, directly addressed by setting the SameSite attribute on cookies.

prevent

Requires timely remediation of the identified software flaw that omits required cookie security attributes.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.DS-02 mostly match
prevents

Setting the Secure attribute is a direct mechanism for protecting sensitive session data in transit over HTTPS.

PR.PS-01 mostly match
prevents

Enforcing hardened configuration baselines includes requiring the Secure flag on sensitive cookies.

PR.PS-06 mostly match
prevents

Secure SDLC practices explicitly require correct use of security attributes such as the cookie Secure flag.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

detects

Security testing can detect missing SameSite attributes but does not prevent the weakness.

mitigates

Use of cryptography control mandates encryption in transit, which HTTPS provides, but does not specifically require the Secure cookie attribute.

prevents

Application security requirements can include cookie security settings, but the control is broader and does not explicitly mandate the Secure attribute.

prevents

Secure coding practices directly prevent missing the Secure attribute on sensitive cookies, though the control covers many other coding issues.

degrades

Secure authentication control requires protection of session credentials, directly addressed by setting the Secure flag on sensitive cookies.

References