VulnerabilityPublished 16 Jan 2026Updated 27 Jan 2026

CVE-2026-0696: ConnectWise PSA · Sensitive Cookie Without 'HttpOnly' Flag

Affects ConnectWise PSASource CVE Database V5

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 33% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 16 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
ConnectWisePSA	Affected =All versions prior to 2026.1	Fixed in–

AI-suggested

The primary mitigation is to upgrade ConnectWise PSA to version 2026.1 or later, where the HttpOnly flag is properly set on session cookies. Until patching is possible, organizations should implement strict Content Security Policies (CSP) to reduce the risk of XSS attacks that could exploit this vulnerability. Regular security assessments and penetration testing should focus on identifying and remediating XSS vulnerabilities in web applications integrated with ConnectWise PSA. Additionally, user awareness training to recognize phishing attempts can reduce the likelihood of successful exploitation. Network-level protections such as web application firewalls (WAFs) configured to detect and block malicious scripts can provide an additional layer of defense. Monitoring for unusual session activity and implementing multi-factor authentication (MFA) can help mitigate the impact of compromised sessions. Finally, reviewing and minimizing the scope of cookies and their attributes (e.g., Secure flag, SameSite attribute) can further harden session security.

Description

In ConnectWise PSA versions older than 2026.1, certain session cookies were not set with the HttpOnly attribute. In some scenarios, this could allow client-side scripts access to session cookie values.

Impact

For European organizations, the exposure of session cookies without the HttpOnly flag can lead to session hijacking, allowing attackers to impersonate legitimate users and gain unauthorized access to sensitive business information, client data, and internal management tools. This can result in data breaches, loss of customer trust, and compliance violations under regulations such as GDPR. MSPs and IT service providers using ConnectWise PSA are particularly at risk, as compromise of their management platform could cascade to multiple client environments. The vulnerability's requirement for user interaction means phishing or social engineering campaigns could be effective attack vectors. Additionally, organizations with less mature web security practices or lacking robust XSS protections are more vulnerable. The impact is heightened in sectors with critical IT service dependencies, such as finance, healthcare, and government institutions across Europe.

CWE-1004Sensitive Cookie Without 'HttpOnly' Flag (opens in a new tab)
Variant weaknessLikelihood of exploit: MediumOWASP Top 10 A02:2025: Security Misconfiguration (opens in a new tab)
The product uses a cookie to store sensitive information, but the cookie is not marked with the HttpOnly flag.
Implementation
Leverage the HttpOnly flag when setting a sensitive cookie in a response.
OWASP Cheat Sheets
Cross-Site Request Forgery Prevention (opens in a new tab)
Session Management (opens in a new tab)
OWASP ASVS 4.0.3
V3.4.2 (opens in a new tab)
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 27 Jan 2026, 19:15 UTC

WeaknessesCWE-1004

Technical details

References

Community reviews

Related threats