Your OPC UA stack is a supply-chain risk. Here is how to manage it.
By Etienne Rossignon, CEO of Sterfive and creator of node-opcua. 10 November 2026.
node-opcua is downloaded about 500,000 times a month. It runs inside edge gateways, MES connectors, SCADA bridges and test benches at companies such as ABB, Siemens, Renault, Tulip and Litmus. Many of those systems will still be in production in 2040.
I created node-opcua in 2014 and have maintained it ever since. If your products or plants depend on it, one question belongs on your risk register: who is contractually responsible for fixing the next vulnerability in your OPC UA stack, and how fast?
For most users today, the honest answer is nobody. This article explains why that has become a business and compliance risk, and how to close it with a single purchase order.
The risk you did not budget for
An OPC UA stack is not a utility library. It sits at the network boundary of your plant, parses untrusted binary input, negotiates encryption and manages X.509 certificates. When it fails, it fails at the exact place attackers look first.
It also never stands still. Node.js ships a new LTS line every year, OpenSSL changes underneath it, the OPC UA specification evolves, and older security policies are deprecated. A stack that is not actively maintained becomes a liability within two or three years, while the machine it runs on is expected to last fifteen.
Using node-opcua without a support relationship means:
- You learn about a vulnerability when it becomes public, at the same moment as attackers.
- The timing of the fix depends on the goodwill and free time of the maintainer.
- Nobody guarantees a patch for the version you actually ship.
- During an incident, there is no one you are entitled to call.
The CRA makes it your problem, not the maintainer's
The EU Cyber Resilience Act largely exempts open source developed outside commercial activity. The obligations do not disappear. They move to you, the manufacturer who integrates that code into a product placed on the EU market.
- Manufacturers must exercise due diligence on third-party components, open source included.
- Since 11 September 2026, actively exploited vulnerabilities must be reported to the authorities.
- From 11 December 2027, the full requirements apply: vulnerability handling, security updates over the support period, and a software bill of materials.
IEC 62443-4-1 asks the same of component suppliers: a defined patch process and a known source of security updates. "It is open source, someone will fix it" is not evidence an auditor accepts. A support contract with the maintainer is.
Why the usual answers fall short
Companies that spot this risk usually reach for one of four answers. Each solves part of the problem and leaves the core of it open.
| Option | What you get | What stays open |
|---|---|---|
| Donations or sponsorship | Goodwill, a healthier project | No SLA, no named contact, rarely fits procurement |
| Fork and maintain in-house | Full control | Needs OPC UA and cryptography expertise; drifts from upstream fixes |
| Rewrite on a commercial C/C++ stack | A contracted supplier | A costly migration, and you lose your Node.js and TypeScript ecosystem |
| Wait for public or foundation grants | Funded hardening of the project | Nothing specific to your versions, deadlines or incidents |
What you actually need is ordinary: a supplier relationship with the people who maintain the code you ship.
A supported dependency in one purchase order
Sterfive is the company behind node-opcua since 2017. A node-opcua support membership turns node-opcua from an unmanaged dependency into a contracted one, with a standard invoice your procurement team already knows how to process.
| Membership | Built for | Price (ex VAT) | Includes |
|---|---|---|---|
| SME | SMEs and single-product teams | from 5 000 € / year | Private GitLab space with the maintainers, priority fixes shipped upstream, security advisories before public disclosure, CRA due-diligence statement |
| Enterprise | Larger organisations, several products or sites | from 14 900 € / year | Everything in SME, plus guaranteed response times, tested and signed builds, a maintained upgrade path, SBOM and vulnerability statement per release |
| Gold Partnership | OEMs and platform vendors shipping node-opcua at scale | from 25 000 € / year | Everything in Enterprise, plus a named contact, architecture reviews, priority on roadmap requests, public partner recognition |
Every membership also funds the MIT-licensed core that the whole industrial community relies on. You buy a guarantee for your products and strengthen the project at the same time.
Five questions your CISO will ask about node-opcua
If you use node-opcua in production, forward this list to whoever owns product security. If two or more answers are "we don't know", the risk is unmanaged.
- Which version of node-opcua do we ship, and is it still receiving security fixes?
- Who notifies us when a vulnerability is found, and do we hear before or after it is public?
- Can we produce an SBOM and a vulnerability statement for our OPC UA stack on request?
- How are OPC UA certificates issued, renewed and revoked across our fleet?
- If a critical flaw is exploited tomorrow, who do we call, and what does the contract say?
Frequently asked questions
Does the Cyber Resilience Act apply to node-opcua? The CRA largely exempts open source developed outside commercial activity. The obligations move to the manufacturer that integrates node-opcua into a product placed on the EU market. That manufacturer must exercise due diligence on the component and handle its vulnerabilities.
Who fixes security vulnerabilities in node-opcua? node-opcua is maintained by Sterfive. Without a support membership, fixes depend on the maintainer's free time and arrive when the vulnerability is public. Support members receive advisories before public disclosure and fixes for the versions they ship.
How much does node-opcua support cost? Sterfive support memberships start from 5 000 € per year for SMEs, 14 900 € per year for larger organisations, and 25 000 € per year for a Gold Partnership, ex VAT.
Next step: a 30-minute call
Book a call with me. In 30 minutes we map where node-opcua runs in your products, which versions you ship, and which membership fits. If question 4 above was hard to answer, we will also look at certificate management, where OPC UA GDS by Sterfive removes the manual work.
Request support or book a call
Not ready for a contract yet? Corporate sponsorship through GitHub Sponsors keeps the core healthy. It carries no SLA, but it is a good first step while your procurement process runs.
Related Sterfive articles