CVE-2024-25626: Yocto Project is an open source collaboration project that helps developers create custom Linux-based systems

This month

HIGH 8.8WATCHLISTUPGRADE

CVE-2024-25626 is a high-severity flaw (CVSS 8.8) affecting yocto. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Yocto Project is an open source collaboration project that helps developers create custom Linux-based systems regardless of the hardware architecture. In Yocto Projects Bitbake before 2.6.2 (before and included Yocto Project 4.3.1), with the Toaster server (included in bitbake) running, missing input validation allows an attacker to perform a remote code execution in the server's shell via a crafted HTTP request. Authentication is not necessary.

Why this priority

High severity
On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score	8.8 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	1.2% (top 32%)
CISA exploited list	No
Weakness	CWE-78
Published	2024-02-19
Last modified	2026-06-17

Publisher (CNA): GitHub, Inc. · Vendor: linuxfoundation

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2024-02-19 20:15 UTCPublished CVE record published
2026-06-17 07:16 UTCUpdated Record last modified

linuxfoundation yocto UPGRADE

Affected: < 3.1.31 · >= 3.2 and < 4.0.16 · >= 4.1 and < 4.3.2

Fixed in: 3.1.31, 4.0.16, 4.3.2

Safe to downgrade to: a release before 3.2

1. Check installed version

apt-cache policy yocto || rpm -q yocto || yocto --version

2. UPGRADE to 3.1.31 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade yocto

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade yocto

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 3.2 (Debian / Ubuntu)

apt-cache madison yocto sudo apt install yocto=<VERSION_BEFORE_3.2> sudo apt-mark hold yocto

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list yocto sudo dnf downgrade yocto-<VERSION_BEFORE_3.2> sudo dnf versionlock add yocto

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-25626?

yocto: upgrade to 3.1.31, 4.0.16, 4.3.2. Exact commands for each OS are on this page.

Is CVE-2024-25626 being exploited?

CVE-2024-25626 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-25626 affect?

CVE-2024-25626 affects yocto. Severity is high (CVSS 8.8). Yocto Project is an open source collaboration project that helps developers create custom Linux-based systems regardless of the hardware architecture. In Yocto Projects Bitbake before 2.6.2 (before and included Yocto Project 4.3.1), with th

How urgent is CVE-2024-25626?

Priority 53/100. High severity; On your watchlist

Related CVEs

CVE-2025-20746 MEDIUM 6.7 DOWNGRADE DOWNGRADE In gnss service, there is a possible out of bounds write due to an incorrect bounds check
CVE-2025-20747 MEDIUM 6.7 DOWNGRADE DOWNGRADE In gnss service, there is a possible out of bounds write due to an incorrect bounds check
CVE-2026-20435 MEDIUM 4.6 DOWNGRADE DOWNGRADE In preloader, there is a possible read of device unique identifiers due to a logic error
CVE-2025-61611 HIGH 7.5 MITIGATE In modem, there is a possible improper input validation
CVE-2025-20765 MEDIUM 4.7 DOWNGRADE MITIGATE In aee daemon, there is a possible system crash due to a race condition

References

← Back to latest CVEs