This CVE reveals a critical design flaw in CatchPulse: the kernel filter communication port accepts connections from any local process, effectively allowing untrusted code to bypass the security policy it's supposed to enforce. If you have any local code execution ability—whether from malware, a compromised credential, or another vulnerability—you can send messages directly to the enforcement layer and disable or manipulate protection policies. The CVSS 8.4 score significantly understates the real risk in enterprise environments where CatchPulse is the primary endpoint controls. A compromised workstation in a fleet where CatchPulse enforces application whitelisting doesn't just evade one policy—it potentially seizes the enforcement layer itself, turning the security product into a weapon that whitelists malware as 'signed known good' code. Verify immediately whether the kernel filter port (check process enumeration for CatchPulse-related listening ports) permits connections from non-admin processes—this is your blast radius indicator. If you're running CatchPulse in containerized or multi-tenant environments, assess whether container workloads can reach this port; if so, the exploit path collapses from 'malware on my workstation' to 'any workload on this host,' dramatically expanding exposure. Prioritize patching aggressively—the EPSS low-probability framing is misleading because the actual exposure window isn't days but potentially years across your install base. Beyond patching, examine whether CatchPulse has compensating kernel-level authentication downstream; if the port is the only chokepoint with no secondary validation, your risk profile is worse than the CVSS suggests. This vulnerability class has recurred across endpoint security products for decades because architects treat localhost as a non-adversarial trust domain—an assumption that fails in any multi-user, BYOD, or shared-infrastructure environment.
CVE-2026-55978
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 · uneditedAn improper access control vulnerability in CatchPulse could allow a non-administrative local attacker to connect to an unrestricted kernel filter communication port and bypass CatchPulse's security policy enforcement.
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 analysisThe application fails to correctly restrict what a user can do or reach, so functions or resources are available to people who should not have them. Attackers simply probe for the paths where the check is missing or wrong. The fix is to enforce access-control decisions consistently on every request, evaluated against the acting user rather than assumed from context.
General guidance for the improper access control class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →
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
- Changed
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:H
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.
From vendor dataThere is no version to upgrade to and no patch to apply. Every affected install stays exposed until the vendor ships a fix — or somebody else builds one.
Free. We build fixes in the order the community asks for them — and we’ll tell you the moment this one lands.
We develop and verify an original fix where the vendor hasn’t, from $1,950. Deployed to your staging first — never straight to production.
Scope it with usSee what else the community needs solved on the solutions-needed board.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-55978 — 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 sourcesThis CVE reveals a critical design flaw in CatchPulse: the kernel filter communication port accepts connections from any local process, effectively allowing untrusted code to bypass the security policy it's supposed to enforce. If you have any local code execution ability—whether from malware, a compromised credential, or another vulnerability—you can send messages directly to the enforcement layer and disable or manipulate protection policies. The CVSS 8.4 score significantly understates the real risk in enterprise environments where CatchPulse is the primary endpoint controls. A compromised workstation in a fleet where CatchPulse enforces application whitelisting doesn't just evade one policy—it potentially seizes the enforcement layer itself, turning the security product into a weapon that whitelists malware as 'signed known good' code. Verify immediately whether the kernel filter port (check process enumeration for CatchPulse-related listening ports) permits connections from non-admin processes—this is your blast radius indicator. If you're running CatchPulse in containerized or multi-tenant environments, assess whether container workloads can reach this port; if so, the exploit path collapses from 'malware on my workstation' to 'any workload on this host,' dramatically expanding exposure. Prioritize patching aggressively—the EPSS low-probability framing is misleading because the actual exposure window isn't days but potentially years across your install base. Beyond patching, examine whether CatchPulse has compensating kernel-level authentication downstream; if the port is the only chokepoint with no secondary validation, your risk profile is worse than the CVSS suggests. This vulnerability class has recurred across endpoint security products for decades because architects treat localhost as a non-adversarial trust domain—an assumption that fails in any multi-user, BYOD, or shared-infrastructure environment.
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-55978 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
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