# CVE-2007-2026: Denial of service in n/a

> Attackers can cause denial of service via CPU exhaustion by submitting crafted documents with many line feeds to applications using the vulnerable GNU regex library.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:N/I:N/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 13 Apr 2007
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2007-2026, GHSA-q6xr-rq9m-h889

## What is CVE-2007-2026?

CVE-2007-2026 is a high-severity denial of service vulnerability in n/a, published on 13 Apr 2007. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The gnu regular expression code in file 4.20 allows context-dependent attackers to cause a denial of service (CPU consumption) via a crafted document with a large number of line feed characters, which is not well handled by OS/2 REXX regular expressions that use wildcards, as originally reported for AMaViS.

## Which versions are affected by CVE-2007-2026?

It affects 2 products.


Products: Amavis Virus Scanner, Gentoo File.

## How do I fix CVE-2007-2026?

Upgrade to a fixed version.

## Is CVE-2007-2026 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-1999-1512](https://insights.sbomify.com/CVE-1999-1512/): Command injection in n/a (critical 10.0)
- [CVE-2002-1109](https://insights.sbomify.com/CVE-2002-1109/): Denial of service in n/a (low 2.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-2026 and fix it if it is affected.

What it is: CVE-2007-2026 is a high-severity denial of service vulnerability in n/a, published on 13 Apr 2007. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2007-2026 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-2007-2026/ (Markdown: https://insights.sbomify.com/CVE-2007-2026/index.md)
```

## Sources

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

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