dbcve.org
Memory Buffer Bounds ErrorWeakness · CWE-119

CVE-2026-15506

HIGH · 7.8 CVSS v3.1 Published 2026-07-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click 5 weeks old

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 · unedited
A security vulnerability has been detected in SecureAge CatchPulse up to 10.9.3. The affected element is an unknown function in the library saappctl.sys of the component Driver. Such manipulation leads to heap-based buffer overflow. An attack has to be approached locally. The exploit has been disclosed publicly and may be used. Upgrading to version 10.10.0 is sufficient to fix this issue. You should upgrade the affected component. The vendor was contacted early about this disclosure.

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 confidence

Heap-based buffer overflow vulnerability in the saappctl.sys kernel-mode driver component of SecureAge CatchPulse (versions up to 10.9.3). The flaw exists in an unspecified function within the driver, allowing local attackers to overflow heap memory. Given the driver operates in kernel mode, successful exploitation could lead to privilege escalation or system compromise.

MitigationUpgrade CatchPulse to version 10.10.0 to obtain the patched saappctl.sys driver. As this is a security product driver, verify compatibility with production systems before deployment and ensure proper testing in a staging environment.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify SecureAge CatchPulse installation and version
    Check the installed version of CatchPulse using system inventory tools or look for the product in Add/Remove Programs (Windows) or package manager (Linux). Compare the installed version against the affected range (versions up to and including 10.9.3).
    Affected if CatchPulse version is 10.9.3 or lower.
  2. Locate the saappctl.sys driver file
    Search for the saappctl.sys file in the CatchPulse installation directory, typically found under the product's driver or system folder. Use file system search or review the installation path.
    Affected if The saappctl.sys driver file exists in a CatchPulse installation directory.
  3. Check driver file version
    Right-click the saappctl.sys file, select Properties, and examine the File Version field. Alternatively, use the 'ver' command or a file version inspection utility on the driver file.
    Affected if The driver file version corresponds to CatchPulse 10.9.3 or earlier.
  4. Verify driver loaded status
    Open an elevated command prompt and run 'sc query saappctl' or check Device Manager for the SecureAge driver under 'System devices'. The driver must be loaded for the vulnerability to be exploitable.
    Affected if The saappctl.sys driver is currently loaded in memory.

A system is affected if SecureAge CatchPulse version 10.9.3 or earlier is installed with the saappctl.sys driver present, especially if the driver is currently loaded.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade CatchPulse to version 10.10.0 to obtain the patched saappctl.sys driver. As this is a security product driver, verify compatibility with production systems before deployment and ensure proper testing in a staging environment.

Recommended fix High confidence

10.10.0

  1. 1. Check the current version of SecureAge CatchPulse installed on the system
  2. 2. Download SecureAge CatchPulse version 10.10.0 from the official SecureAge website or trusted distribution channel
  3. 3. Close any running applications that interact with CatchPulse
  4. 4. Run the installer for version 10.10.0
  5. 5. Follow the on-screen prompts to complete the upgrade
  6. 6. Restart the system if prompted by the installer
  7. 7. Verify that the installed version is 10.10.0 and that the saappctl.sys driver is functioning correctly

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-15506 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-15506 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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