CVE-2026-0696
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceIn ConnectWise PSA versions prior to 2026.1, session cookies are not configured with the HttpOnly flag, which normally prevents client-side JavaScript from accessing cookie values. This could enable an attacker who successfully exploits a cross-site scripting (XSS) vulnerability to steal session cookies and impersonate users.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2026.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify ConnectWise PSA versionLocate the version number in the product (typically found in Help > About, Settings > System Info, or the login page footer). Compare this version to 2026.1.Affected if The installed version is any release prior to 2026.1 (e.g., 2025.x, 2024.x, etc.).
-
Capture a session cookie from the applicationLog into ConnectWise PSA and capture a session cookie using browser Developer Tools (Application tab > Cookies), curl with credentials, or a proxy tool like Burp Suite.Affected if A session cookie is successfully retrieved from the login process.
-
Inspect the Set-Cookie header for HttpOnly flagExamine the Set-Cookie response header when authenticating, or inspect the cookie properties in browser dev tools. Look for the HttpOnly attribute in the cookie definition.Affected if The session cookie does NOT contain the HttpOnly flag, or the HttpOnly attribute is missing from the Set-Cookie header.
-
Verify if the cookie is accessible to JavaScriptIn browser dev tools console, attempt to access the session cookie via document.cookie. If the session cookie value appears in the output, it is accessible to JavaScript.Affected if The session cookie value is returned by document.cookie, indicating it lacks HttpOnly protection.
You are affected if ConnectWise PSA version is below 2026.1 AND session cookies are missing the HttpOnly flag, as confirmed by inspecting cookie headers or verifying JavaScript access.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2026.1
Upgrade ConnectWise PSA to version 2026.1 or later where the HttpOnly attribute is properly applied to session cookies. As a temporary workaround, consider deploying a WAF or reverse proxy that can inject the HttpOnly flag into Set-Cookie headers.
2026.1
- Upgrade ConnectWise Professional Service Automation to version 2026.1 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-0696 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-0696 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data