# CVE-2021-27138: Other in n/a

> The U-Boot bootloader mishandles unit addresses in FIT images, potentially allowing attackers to execute arbitrary code during the boot process.

- **Severity:** High 7.8 (`CVSS:3.1/AC:L/AV:L/A:H/C:H/I:H/PR:N/S:U/UI:R`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 17 Feb 2021
- **Updated:** 3 Nov 2025
- **Also known as:** ALPINE-CVE-2021-27138, DEBIAN-CVE-2021-27138, GHSA-grrh-mjp7-g52c, UBUNTU-CVE-2021-27138

## What is CVE-2021-27138?

CVE-2021-27138 is a high-severity vulnerability in n/a, published on 17 Feb 2021. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

The boot loader in Das U-Boot before 2021.04-rc2 mishandles use of unit addresses in a FIT.

## Which versions are affected by CVE-2021-27138?

It affects 1 product.


Products: Denx U-Boot.

## How do I fix CVE-2021-27138?

Upgrade to a fixed version.

## Is CVE-2021-27138 being exploited?

There is no known exploitation of CVE-2021-27138 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2022-34835](https://insights.sbomify.com/CVE-2022-34835/): Integer overflow in n/a (critical 9.8)
- [CVE-2022-30767](https://insights.sbomify.com/CVE-2022-30767/): Memory corruption in n/a (critical 9.8)
- [CVE-2020-8432](https://insights.sbomify.com/CVE-2020-8432/): Use after free in n/a (critical 9.8)
- [CVE-2019-14192](https://insights.sbomify.com/CVE-2019-14192/): Integer overflow in n/a (critical 9.8)
- [CVE-2019-14193](https://insights.sbomify.com/CVE-2019-14193/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-27138 and fix it if it is affected.

What it is: CVE-2021-27138 is a high-severity vulnerability in n/a, published on 17 Feb 2021. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2021-27138 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2021-27138/ (Markdown: https://insights.sbomify.com/CVE-2021-27138/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-27138
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-27138
- OSV: https://osv.dev/vulnerability/CVE-2021-27138

---
From sbomify Insights: https://insights.sbomify.com/CVE-2021-27138/
Summaries are generated and may contain mistakes; the official description above is the record.