CVE-2007-2026 json
The gnu regular expression code in file 4.20 allows context-dependent attackers to cause a denial of service (CPU consumption) via a crafte…
published 2007-04-13 19 y ago modified 2026-06-16 4 mo ago also EUVD-2007-2021
- cvss
- 7.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.1%
- EPSS 2.1% chance of exploitation in 30 days, percentile 81%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- file Debian 14, Debian 13, Debian 12 4.20-6
debian advisories DEBIAN-CVE-2007-2026
Exploit prediction
2.09% chance of exploitation in the next 30 days, higher than 81% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.8 | AV:N/AC:L/Au:N/C:N/I:N/A:C |
References
-
gentoo.org
/security/en/glsa/glsa-200704-13.xml
vendor-advisory
-
mandriva.com
/security/advisories?name=MDKSA-2007:114
vendor-advisory
- bugs.gentoo.org /show_bug.cgi?id=174217
-
secunia.com
/advisories/24918
third-party-advisory
- sourceforge.net /mailarchive/forum.php?thread_name=755AF709E5B77E6EA58479D5%40foxx.lsit.ucsb.edu&forum_name=amavis-user
- issues.rpath.com /browse/RPL-1311
- amavis.org /security/asa-2007-3.txt
-
secunia.com
/advisories/25544
third-party-advisory
-
secunia.com
/advisories/25578
third-party-advisory
-
securityfocus.com
/archive/1/469520/30/6420/threaded
mailing-list
-
vupen.com
/english/advisories/2007/2071
vdb-entry
-
secunia.com
/advisories/25394
third-party-advisory
-
securityfocus.com
/bid/24146
vdb-entry
Sources
- CVE List CVE-2007-2026
- NVD CVE-2007-2026
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.