Security Advisories

This page lists security advisories for Alicat products. An advisory is published when a security vulnerability in an Alicat product has been confirmed and a fix or mitigation is available, or when users need to know about a vulnerability that is being actively exploited even before a fix exists.

Every advisory we publish is listed on this page. Each has a permanent reference in the form ALICAT-SA-YYYY-NNN, which we use in release notes and in any correspondence about the issue.

To report a vulnerability, see alicat.com/security. Do not use this page to report; use [email protected].

Current advisories

No advisories have been published. This page was last reviewed on September 11, 2026.

How to get notified

• Email. Subscribe at alicat.com/newsletter-sign-up to receive every advisory by email. You can unsubscribe at any time. We use the address only for security notifications.
• RSS. A feed of all advisories is available at alicat.com/security-advisories/feed.xml.
• Distributors. We send every advisory to our authorized distributors so they can pass it to their customers.
• Direct notice. Where we become aware that a vulnerability is being actively exploited, or of a security incident affecting an Alicat product, we contact affected users directly using the contact details we hold for them, in addition to publishing here.

Subscribing is the most reliable way to hear from us. Where we hold your contact details, for example because you bought directly from Alicat or have an open support case, we may also contact you directly.

What each advisory tells you

• Reference, publication date, and the date of the latest revision.
• The CVE identifier, where one has been assigned.
• A severity rating and CVSS score (see below), and whether we are aware of the vulnerability being exploited.
• The products, models, and versions affected, and the conditions under which a system is exposed.
• The version that contains the fix and where to obtain it, or the mitigation to apply if no fix is available yet.
• A plain description of the issue and what an attacker could do with it.
• Credit to the reporter, where they have agreed to be named.

Advisories may be updated after publication, for example when a fix becomes available for a further product or when a CVE is assigned. The revision number and date in the first column change when that happens.

Alicat may also make advisories available in a structured, machine-readable format.

Severity ratings

Alicat rates each advisory using the Common Vulnerability Scoring System (CVSS) version 3.1 base score, considering the product in its intended use.

The CVSS score is a guide. Your own risk depends on how the product is deployed, for example whether an instrument or mixer is reachable from a network other than the one it was installed on. Each advisory says what conditions are needed to exploit the vulnerability so you can judge that.

Products no longer supported

Where a vulnerability affects a product that has passed the end of its security support period, Alicat may publish an advisory describing the vulnerability and any available mitigation without providing a fix. The advisory will say so. Support end dates are shown on each product page and in the documentation supplied with the product.

Availability of this page

Advisories remain available on this page for at least ten years after publication or for the support period of the affected product, whichever is longer. Advisory references do not change once published.

Legal notices

Advisories describe the information available to Alicat at the time of publication and may be updated as more becomes known. They are provided to help users protect their systems and are not a warranty. Nothing in an advisory changes the terms of sale, license agreements, or warranties that apply to Alicat products.

Version 1.2, published September 11, 2026.