Windows crash via undisclosed stack overflow
Published Apr 30, 2026 · Updated Apr 30, 2026
Stack-based buffer overflow in Absolute Secure Access Windows client before 14.50 allows local users to crash Windows with a blue screen. Absolute has not disclosed the affected client component, the input that reaches it, or the unchecked operation that overruns the stack buffer. Exploitation requires local control of the client; the disclosed outcome is an operating-system crash, while the vendor does not explain the low integrity effect represented in its score.
Summary
What happened
Stack-based buffer overflow in Absolute Secure Access Windows client before 14.50 allows local users to crash Windows with a blue screen. Absolute has not disclosed the affected client component, the input that reaches it, or the unchecked operation that overruns the stack buffer. Exploitation requires local control of the client; the disclosed outcome is an operating-system crash, while the vendor does not explain the low integrity effect represented in its score.
The record
- CVE
- CVE-2026-33452
- Published
- Apr 30, 2026
- Updated
- Apr 30, 2026
- Vendor
- Absolute Security
- Product
- Absolute Secure Access
- Classifications
- CWE-121, T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 30, 2026CVE publishedPublication date reported by the CVE source.
- Apr 30, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <14.50
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo