CVE-2026-33450
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-33450 is an out of bounds read vulnerability in the Secure Access MacOS client prior to 14.50. Attackers with control of a modified server can send a malformed packet to the client causing a denial of service.
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 · high confidenceOut of bounds read vulnerability in Secure Access MacOS client versions prior to 14.50. An attacker controlling a modified server can send a malformed packet to the client, triggering an out-of-bounds memory read that causes denial of service.
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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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.
-
Identify installed Secure Access versionOpen Finder, navigate to /Applications, locate 'Absolute Secure Access' or 'Secure Access' app, right-click and select 'Get Info', or use command: defaults read /Applications/Secure\ Access.app/Contents/Info CFBundleShortVersionStringAffected if Version displayed is less than 14.50 (e.g., 14.49, 14.0, 13.x)
-
Check version via system_profilerRun command: system_profiler SPApplicationsPath | grep -i 'Secure Access' in Terminal to retrieve installed application version detailsAffected if Listed version is below 14.50
-
Verify client is installed and activeCheck if the application exists in /Applications folder and examine running processes with: ps aux | grep -i 'secure access' or check for the client menu bar icon/statusAffected if Client is installed and running, with version below 14.50, making it vulnerable to malformed packets from a compromised server
If the installed Absolute Secure Access MacOS client version is below 14.50 and the client is active or configured for connections, the environment is affected by this out-of-bounds read vulnerability.
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 Secure Access MacOS client to version 14.50 or later to remediate this vulnerability.
Secure Access MacOS client version 14.50 or later
- Check the current version of the Secure Access client installed on the MacOS system
- Download the Secure Access MacOS client version 14.50 or later from the vendor's official website (www.absolute.com)
- Quit any running instances of the Secure Access client
- Install the updated Secure Access client version 14.50 or later
- Verify the installed version is 14.50 or higher to confirm the remediation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-33450 — 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-33450 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