How severe is CVE-2006-3747?

No CVSS score has been assigned to CVE-2006-3747 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2006-3747?

Affected package information for CVE-2006-3747 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2006-3747?

No fixed release is recorded for CVE-2006-3747 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.

How do I detect CVE-2006-3747 in my code and dependencies?

Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

How do I mitigate CVE-2006-3747 if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is CVE-2006-3747 actively exploited in the wild?

Yes. There are 5 known exploit references for CVE-2006-3747, including 4 documented proof-of-concept exploits on Exploit-DB and 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2006-3747?

CVE-2006-3747 has an EPSS (Exploit Prediction Scoring System) score of 96.6%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is CVE-2006-3747?

CVE-2006-3747 is classified as CWE-189 (CWE-189). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2006-3747 published, and has it been updated?

CVE-2006-3747 was published on July 28, 2006 and was last updated on April 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Not in CISA KEV

CVE-2006-3747 — Red Hat

CVE-2006-3747 is a CWE-189 vulnerability. 5 public exploit references exist, so weaponization risk is real. No vendor fix is recorded yet; mitigation options are listed below.

Published

Jul 28, 2006

Updated

Apr 10, 2026

Affected

3 products

Patched

See advisory

Exploits

5 known

Exploitation data as of Oct 22, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

96.6%probability of exploitation in next 30 days

Very High Risk0.00%

Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Description

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.

Affected Products

3 products · 7 configurations

Application

http serverapache

≥ 2.2.0 && < 2.2.3

range

ubuntu linuxcanonical

3 versions

5.045.106.06

debian linuxdebian

1 version

3.1

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-3680remotewindows_x86✓ Verified

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

by axis · Apr 7, 2007

Exploit-DB Source

EDB-2237remotemultiple✓ Verified

Apache < 1.3.37/2.0.59/2.2.3 mod_rewrite - Remote Overflow

by Jacobo Avariento · Aug 21, 2006

Exploit-DB Source

EDB-3996remotewindows✓ Verified

Apache 2.0.58 mod_rewrite (Windows 2003) - Remote Overflow

by fabio/b0x · May 26, 2007

Exploit-DB Source

EDB-16752remotewindows✓ Verified

Apache mod_rewrite - LDAP protocol Buffer Overflow (Metasploit)

by Metasploit · Feb 15, 2010

Exploit-DB Source

Detection & mitigation playbook

Vulnerability

Detect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Remediation status
No fixed release is recorded for CVE-2006-3747 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.
Mitigate without a patch
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Ubuntu

USN-328-1Ubuntu

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2006-3747 in your dependencies?

Find it across , including transitive dependencies.

Scan my dependencies How O3 SCA works

CVE-2006-3747 — Red Hat

EPSS Exploitation Probability

Description

Affected Products

Detection & mitigation playbook

Detect

Remediation status

Mitigate without a patch

Fixing This On Your OS

Frequently Asked Questions

Is CVE-2006-3747 in your dependencies?