RT-Labs Becomes CVE Numbering Authority

The embedded software developer can now assign CVE IDs and publish CVE Records for its own products and certain third-party dependencies.

Updated on Nov. 19, 2026 in Cybersecurity

RT-Labs Becomes CVE Numbering Authority

RT-Labs was designated a CVE Numbering Authority under the European Union Agency for Cybersecurity Root, enabling it to assign CVE IDs and publish CVE Records for its own products. The designation was announced on November 19, 2026.

Why it matters

The authority allows RT-Labs to manage CVE assignment directly rather than relying on external organisations, which reduces its response times. Downstream OEMs, vendors and security teams use CVE IDs to assess risks and apply software updates.

RT-Labs develops software for embedded systems, including middleware components, platforms and test automation tools. Its CNA scope covers its own products and third-party dependencies not within the scope of another CNA, though the extraction does not detail how many components fall into each category.

The players

RT-Labs

RT-Labs is a software developer focused on embedded systems, providing middleware components, platforms and test automation tools.

European Union Agency for Cybersecurity

The European Union Agency for Cybersecurity, known as ENISA, is the EU body that works to improve cybersecurity across member states and operates the EUVD CNA Root under which RT-Labs was designated.

The details

RT-Labs was designated a CVE Numbering Authority under the European Union Agency for Cybersecurity Root and can now assign CVE IDs and publish CVE Records for its own products. The company may also assign CVE IDs to third-party dependencies that fall outside another CNA's scope.

Timeline

  1. November 19, 2026: RT-Labs CVE Numbering Authority designation announced.

The Tech Race

The CVE Program distributes ID-assignment authority across CNAs so vendors can issue identifiers for their own products rather than waiting on a central body. RT-Labs' designation extends that distributed model into the embedded-systems sector, where software is often shipped inside hardware with long support lifecycles.

Developers and security teams that depend on RT-Labs software can expect CVE IDs for its products to be issued directly by the company rather than through an intermediary. This may shorten the time between a discovered vulnerability and a published record that teams use to plan software updates.

The takeaway

Distributed CVE issuance means vendors can publish vulnerability records themselves, so teams tracking embedded software should watch for CVE Records from RT-Labs directly. Checking CVE entries against the products in use helps prioritize patching as new IDs appear.

Further reading

For broader context on how vulnerability identifiers are issued and tracked, explore the Cybersecurity section.

Source note: This article includes information reported by Di.