# CVE-2022-4988: Alien::FreeImage versions through 1.001 for Perl contains several vulnerable libraries

> Alien::FreeImage bundles outdated FreeImage libraries with known vulnerabilities, allowing attackers to exploit these flaws via the Perl module.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 May 2026
- **Updated:** 13 May 2026
- **Also known as:** GHSA-wqrc-gg3r-jw9v

## What is CVE-2022-4988?

CVE-2022-4988 is a high-severity vulnerability in KMX Alien::FreeImage, published on 11 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Alien::FreeImage versions through 1.001 for Perl contains several vulnerable libraries.

Alien::FreeImage contains version 3.17.0 of the FreeImage library from 2017, which has known vulnerabilities such as CVE-2015-0852 and CVE-2025-65803.  The library embeds other images libraries that also have known vulnerabilities.

Weakness: CWE-1395 (Dependency on Vulnerable Third-Party Component)

## Which versions are affected by CVE-2022-4988?


## How do I fix CVE-2022-4988?

No fix has been published for CVE-2022-4988 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-4988 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-4988 and fix it if it is affected.

What it is: CVE-2022-4988 is a high-severity vulnerability in KMX Alien::FreeImage, published on 11 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-4988 in the wild and no public exploit code.

Affected product: KMX Alien::FreeImage. 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-2022-4988/ (Markdown: https://insights.sbomify.com/CVE-2022-4988/index.md)
```

## Sources

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

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