CVE-2026-33451
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 · uneditedCVE-2026-33451 is an arbitrary read/write vulnerability in the Secure Access Windows client prior to 14.50. Attackers with local control of the Windows client can send malformed data to an API and elevate their level of privilege to system.
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 confidenceArbitrary read/write vulnerability in the Secure Access Windows client versions prior to 14.50 allows local attackers with control of the client to send malformed data to an API, achieving SYSTEM-level privilege escalation.
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< 14.50CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
-
Locate the Absolute Secure Access Windows client installationCheck Program Files (typically C:\Program Files\Absolute\Secure Access or C:\Program Files (x86)\Absolute\Secure Access) for the client executable, or find it in Add or Remove ProgramsAffected if The client software is not installed on the system
-
Identify the installed version of Absolute Secure Access clientRight-click the client executable, select Properties, and view the Version tab. Alternatively, open the client application and look for About or Version information in the Help menuAffected if The displayed version number is lower than 14.50 (for example, 14.40, 14.0, etc.)
-
Confirm the client service or application is runningOpen Task Manager and look for processes related to Absolute Secure Access (such as SecureAccess.exe, TPAutoConnSvr.exe, or similar). Also check Services.msc for Absolute-related servicesAffected if The client is actively running or installed as a service, and the version is below 14.50
-
Verify the API communication component is presentCheck for network activity on common Absolute Secure Access ports (TCP 443, 8443) using netstat or check the client configuration files in the installation directory for API endpoint settingsAffected if API communication is enabled and the client version is below 14.50
The system is affected if the Absolute Secure Access Windows client is installed with a version number lower than 14.50, as this is the only condition specified in the affected products and versions.
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 · scoped14.50
Upgrade the Secure Access Windows client to version 14.50 or later to remediate this vulnerability.
14.50
- Upgrade the Secure Access Windows client to version 14.50 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-33451 — 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-33451 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