FreeRTOS in ESP-IDF firmware: identifiers and CRA notes

What it is

FreeRTOS

• Homepage
• Repository

Notes on this component

ESP-IDF's RTOS kernel, Espressif's fork of FreeRTOS-Kernel with a referenced sbom.yml in current ESP-IDF (checked 2026-10-07: the component's sbom_FreeRTOS-Kernel.yml carries exactly cpe:2.3:o:amazon:freertos, confirming the part letter is `o` — NVD files FreeRTOS as an operating system, not an application, which is easy to get wrong by analogy with ordinary libraries). This entry is the fallback for a build where that manifest is missing or unread. It no longer states that single amazon:freertos CPE outright: checked against NVD's 5 live CVEs (CVE-2026-77234..77237, the ARMv7-M/ARMv8-M MPU set), that CPE matched 0 of them, because the records name vendor `freertos` product `FreeRTOS-Kernel`, not `amazon`/`freertos`. The FreeRTOS name-alias entry carries both spellings, so this entry points at the pair `freertos`/`freertos-kernel` and the lookup also tries the `amazon` spelling, instead of one narrower opinion cutting the alias widening short. The part-letter fact above still holds and is the reason this entry's `type` stays `os`.

Where it hides in a firmware SBOM

ESP-IDF records it from the component's own sbom.yml file, so what the SBOM says depends on what that file declares.

The identifiers we assign

PURLpackage URL: a standard way to name a software package

pkg:github/FreeRTOS/FreeRTOS-Kernel@{version}

{version} is filled in from your build.

The SBOM check adds these identifiers to a component your build listed without them.

Honest gaps

Vendor: freertos.

This row has no CPE.

Where this row comes from

https://github.com/espressif/esp-idf-sbom#readme
Checked on 9 October 2026.

Known vulnerabilities

Not checked yet

Vulnerability data changes daily. Check the version you ship in the SBOM check.

CRA notes

• List this component in your SBOM. Annex I, Part II (1): Identify and document components and vulnerabilities, including an SBOMKnow what is in your product. Identify and document its components and their vulnerabilities, including by producing a software bill of materials (SBOM) in a common machine-readable format that covers at least the top-level dependencies.
• Ship the version with no known exploitable vulnerabilities at release. Annex I, Part I (2(a)): Made available without known exploitable vulnerabilitiesWhen you place a release on the market, it must not ship with known vulnerabilities that can be exploited in your product. "Exploitable" means an attacker could effectively use it under practical operating conditions (Article 3(41)), not only in theory or in a lab. The Commission's draft guidance (C(2026) 5252, points 231 to 237; a draft, not binding) gives three ways a vulnerability is "known". One: it is listed in a relevant public vulnerability database, such as the European vulnerability database (EUVD) or another prominent one. Two: you learned of it from information that is not public, for example a security researcher's coordinated disclosure or your own testing and analysis; a vulnerability you know about and have not disclosed still counts. Three: it has been publicly and prominently reported in reliable media, whether specialist security publications or general news. A report is not yet proof: it does not by itself mean the vulnerability can be exploited in practice or applies to your product, so investigate promptly and confirm whether it does. A limited time may pass between the first report and that confirmation. If a vulnerability becomes known shortly before release, you decide from your cybersecurity risk assessment whether the release can go out or the vulnerability must be fixed first. Weigh its severity, exploitability and potential impact, and the risks to the product once in use; you may also weigh the risks of delaying the release, for example because it fixes other exploitable vulnerabilities. After release, the Part II vulnerability handling requirements still apply. Check your components against vulnerability databases before each release, and fix or justify what you find.

Source: Annex I of Regulation (EU) 2024/2847 (Cyber Resilience Act), legal state 2026.10.13-1.

Related ESP-IDF components

No related components yet.

Guides that mention FreeRTOS

• The CRA for ESP-IDF teams: real CPEs out of the box, and the parts they do not cover

Next step

Declarable prepares documentation for you to review. It is not legal advice and not certification. You sign your own declaration of conformity.