# CVE-2021-26825: Integer overflow in n/a

> Integer overflow in Godot Engine allows attackers to execute code or crash the system via crafted TGA image files.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **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:** 8 Feb 2021
- **Updated:** 3 Aug 2024
- **Also known as:** DEBIAN-CVE-2021-26825, GHSA-gp7f-w798-4853, UBUNTU-CVE-2021-26825

## What is CVE-2021-26825?

CVE-2021-26825 is a high-severity vulnerability in n/a, published on 8 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

An integer overflow issue exists in Godot Engine up to v3.2 that can be triggered when loading specially crafted.TGA image files. The vulnerability exists in ImageLoaderTGA::load_image() function at line: const size_t buffer_size = (tga_header.image_width * tga_header.image_height) * pixel_size; The bug leads to Dynamic stack buffer overflow. Depending on the context of the application, attack vector can be local or remote, and can lead to code execution and/or system crash.

Weakness: CWE-190 (Integer Overflow or Wraparound)

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

It affects 1 product.


Products: Godotengine Godot Engine.

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

Upgrade to a fixed version.

## Is CVE-2021-26825 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-26826](https://insights.sbomify.com/CVE-2021-26826/): Memory corruption in n/a (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-26825 is a high-severity vulnerability in n/a, published on 8 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-26825 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-26825/ (Markdown: https://insights.sbomify.com/CVE-2021-26825/index.md)
```

## Sources

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

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