CVE-2006-3747

HIGHCVSS v2 · 7.67.6—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 7.6 — v2 rates that HIGH (v2 bands: LOW 0.0–3.9 / MEDIUM 4.0–6.9 / HIGH 7.0–10.0; v2 has no CRITICAL band). Vector AV:N/AC:H/Au:N/C:C/I:C/A:C. CVSS v2 is an older, coarser metric than v3.1/v4.0 (no Scope, no User Interaction, no Attack Requirements), so it is not directly comparable to a v3 or v4 score. NVD has never re-scored this record under v3. EPSS predicts 96.4% exploitation probability in the next 30 days, which is reflected in EG Risk but does not lift the v2 base. Confidence: LOW.

Sources: epss, nvd_v2
Weaponized
7.6EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • 7 internet-exposed hosts are running an affected version right now
  • High exploitation likelihood — EPSS 97%
  • Public exploit code is available (Metasploit, Exploit-DB (verified), epss top5pct, epss high, public exploit)
CISA-KEV: Not listedEPSS PROB: 97%CVSS v2: 7.6Exploit: Metasploit · Exploit-DB (verified) · epss top5pct · epss high · public exploitExposed: 7

A fix is available — apply it.

Off-by-one error in the ldap scheme handling in the Rewrite module (mod_rewrite) in Apache 1.3 from 1.3.28, 2.0.46 and other versions before 2.0.59, and 2.2, when RewriteEngine is enabled, allows remote attackers to cause a denial of service (application crash) and possibly execute arbitrary code via crafted URLs that are not properly handled using certain rewrite rules.

Live · internet exposure

7 internet-exposed hosts are running an affected version of CVE-2006-3747 right now.

across 3 countries (Japan, United States, Finland)top: http_server
See the live KEV-Exposure radar →Found passively from public internet-scan data — aggregate, host-redacted.

EchelonGraph is the only CVE feed that fuses live vulnerability intelligence with its own live internet-exposure radar — so you see not just that a CVE is exploited, but how much of the internet is exposed to it right now.

CVSS v2.0 (legacy)
7.6HIGHNVD never assigned a CVSS v3 rating to this CVE
EG Score
7.6(low)
EG Risk
77(Track)
EG Risk 77/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity76% × 45%
Exploitation96% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
97%
EPSS %ILE
100%
KEV
Not listed

Published

July 28, 2006

Last Modified

April 16, 2026

References (180)

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuapache2-mpm-threadpool (2.0.54-5ubuntu4.1) @ breezy2026-07-23ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(6 across 5 ecosystems)
Debian:3.1(2)
PackageVulnerable rangeFixed inDependents
apache1.3.33-6, 1.3.33-6sarge11.3.33-6sarge2—
apache22.0.54-4, 2.0.54-52.0.54-5sarge1—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
apache2—2.0.55-4.1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
apache2—2.0.55-4.1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
apache2—2.0.55-4.1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
apache2—2.0.55-4.1—

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 1× in last 7d / 2× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-05 15:21 UTCEPSS rescore
  2. 2026-08-24 11:12 UTCOSV refresh
  3. 2026-08-08 07:26 UTCOSV refresh
  4. 2026-07-26 13:29 UTCEG score recompute▲ 7.60
  5. 2026-07-23 00:51 UTCEG score recompute
  6. 2026-07-23 00:39 UTCVendor advisory
  7. 2026-07-23 00:39 UTCGHSA enrichment
  8. 2026-07-23 00:36 UTCVendor advisory
  9. 2026-07-23 00:36 UTCGHSA enrichment
  10. 2026-07-23 00:36 UTCVendor advisory
  11. 2026-07-23 00:36 UTCGHSA enrichment
  12. 2026-07-23 00:34 UTCVendor advisory
  13. 2026-07-23 00:34 UTCGHSA enrichment
  14. 2026-07-23 00:33 UTCVendor advisory
  15. 2026-07-23 00:33 UTCGHSA enrichment
  16. 2026-07-23 00:33 UTCVendor advisory
  17. 2026-07-23 00:32 UTCGHSA enrichment
  18. 2026-07-23 00:30 UTCGHSA enrichment
  19. 2026-07-23 00:30 UTCEG score recompute▼ 9.00
  20. 2026-07-22 23:55 UTCEG score recompute
  21. 2026-07-22 21:35 UTCEG score recompute
  22. 2026-07-09 19:03 UTCEPSS rescore
  23. 2026-07-08 20:39 UTCOSV refresh
  24. 2026-07-02 14:00 UTCEPSS rescore
  25. 2026-06-25 13:46 UTCEPSS rescore
Show 27 more
  1. 2026-06-24 14:01 UTCEPSS rescore
  2. 2026-06-24 14:01 UTCEPSS rescore
  3. 2026-06-23 21:29 UTCEPSS rescore
  4. 2026-06-23 21:29 UTCEPSS rescore
  5. 2026-06-20 08:12 UTCOSV refresh
  6. 2026-06-15 17:44 UTCEPSS rescore
  7. 2026-06-13 22:56 UTCEPSS rescore
  8. 2026-06-10 22:14 UTCEPSS rescore
  9. 2026-06-10 13:17 UTCEPSS rescore
  10. 2026-06-07 15:21 UTCEPSS rescore
  11. 2026-06-05 22:43 UTCEPSS rescore
  12. 2026-06-05 06:07 UTCEPSS rescore
  13. 2026-06-05 06:07 UTCEPSS rescore
  14. 2026-06-04 13:09 UTCEPSS rescore
  15. 2026-06-04 13:09 UTCEPSS rescore
  16. 2026-06-02 20:10 UTCEPSS rescore
  17. 2026-06-02 20:10 UTCEPSS rescore
  18. 2026-05-31 07:27 UTCEG score recompute
  19. 2026-05-31 07:27 UTCVendor advisory
  20. 2026-05-31 07:27 UTCGHSA enrichment
  21. 2026-05-29 13:40 UTCEPSS rescore
  22. 2026-05-27 13:37 UTCEPSS rescore
  23. 2026-05-27 13:37 UTCEPSS rescore
  24. 2026-05-24 16:42 UTCOSV refresh
  25. 2026-05-20 11:20 UTCEPSS rescore
  26. 2026-05-20 11:20 UTCEPSS rescore
  27. 2026-05-18 21:29 UTCEPSS rescore

Publicly available exploits

(6 references)

Working exploit code is in the public domain (1 Metasploit module) (1 GitHub PoC) (4 Exploit-DB entries). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCdefensahacker/CVE-2006-3747
    First seen Nov 26, 2016

    Information about my advisory on CVE-2006-3747 (Apache mod_rewrite LDAP off-by-one buffer overflow).. At the time, it was the first public working exploit :)

    Open source ↗
  • Exploit-DBEDB-16752✓ verified
    First seen Feb 15, 2010

    Apache mod_rewrite - LDAP protocol Buffer Overflow (Metasploit)

    Open source ↗
  • Exploit-DBEDB-3996✓ verified
    First seen May 26, 2007

    Apache 2.0.58 mod_rewrite (Windows 2003) - Remote Overflow

    Open source ↗
  • Exploit-DBEDB-3680✓ verified
    First seen Apr 7, 2007

    Apache mod_rewrite (Windows x86) - Off-by-One Remote Overflow

    Open source ↗
  • Exploit-DBEDB-2237✓ verified
    First seen Aug 21, 2006

    Apache < 1.3.37/2.0.59/2.2.3 mod_rewrite - Remote Overflow

    Open source ↗
  • Metasploitexploit/windows/http/apache_mod_rewrite_ldap✓ verified
    First seen Jul 28, 2006

    Apache Module mod_rewrite LDAP Protocol Buffer Overflow

    Open source ↗

Frequently asked(4)

What is CVE-2006-3747?
CVE-2006-3747 is a high vulnerability published on July 28, 2006. Off-by-one error in the ldap scheme handling in the Rewrite module (mod_rewrite) in Apache 1.3 from 1.3.28, 2.0.46 and other versions before 2.0.59, and 2.2, when RewriteEngine is enabled, allows remote attackers to cause a denial of service (application crash) and possibly execute arbitrary code…
When was CVE-2006-3747 disclosed?
CVE-2006-3747 was first published in the National Vulnerability Database on July 28, 2006, with the most recent update on April 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2006-3747 actively exploited?
CVE-2006-3747 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 97% probability of exploitation in the next 30 days, which ranks it in the top 0.1% of all scored CVEs.
How do I remediate CVE-2006-3747?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2006-3747, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2006-3747

Explore →

Is Your Infrastructure Affected by CVE-2006-3747?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs