How severe is CVE-2006-3918?

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

Which packages are affected by CVE-2006-3918?

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

How do I fix CVE-2006-3918?

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

How do I detect CVE-2006-3918 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-3918 if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

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

Yes. There are 5 known exploit references for CVE-2006-3918, including 1 documented proof-of-concept exploit on Exploit-DB and 4 in-the-wild exploitations 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-3918?

CVE-2006-3918 has an EPSS (Exploit Prediction Scoring System) score of 95.1%, 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-3918?

CVE-2006-3918 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

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

CVE-2006-3918 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-3918 — Red Hat

CVE-2006-3918 is a Cross-site Scripting (XSS) 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

5 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 ↗

95.1%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

http_protocol.c in (1) IBM HTTP Server 6.0 before 6.0.2.13 and 6.1 before 6.1.0.1, and (2) Apache HTTP Server 1.3 before 1.3.35, 2.0 before 2.0.58, and 2.2 before 2.2.2, does not sanitize the Expect header from an HTTP request when it is reflected back in an error message, which might allow cross-site scripting (XSS) style attacks using web client components that can send arbitrary headers in requests, as demonstrated using a Flash SWF file.

Affected Products

5 products · 8 configurations

Application

http serverapache

≥ 1.3.3 && < 1.3.35

range

ubuntu linuxcanonical

4 versions

6.066.107.047.10

debian linuxdebian

1 version

3.1

enterprise linux serverredhat

1 version

2.0

enterprise linux workstationredhat

1 version

2.0

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-28424remotelinux✓ Verified

Apache 1.3.35/2.0.58/2.2.2 - Arbitrary HTTP Request Headers Security

by Thiago Zaninotti · Aug 24, 2006

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-3918 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.
Mitigate without a patch
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

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.

Red HatModerate

Product	Fixed in	Advisory
Red Hat Certificate System 7.3	`ant-0:1.6.5-1jpp_1rh`	RHSA-2010:0602
Red Hat Enterprise Linux 3	`httpd-0:2.0.46-61.ent`	RHSA-2006:0619
Red Hat Enterprise Linux AS (Advanced Server) version 2.1	see advisory	RHSA-2006:0618
Red Hat Network Proxy v 4.2 (RHEL 3)	`jabberd-0:2.0s10-3.37.rhn`	RHSA-2008:0523
Stronghold 4.0 for Red Hat Enterprise Linux AS (version 2.1)	see advisory	RHSA-2006:0692

Ubuntu

USN-575-1Ubuntu

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2006-3918 in your dependencies?

Find it across , including transitive dependencies.

Scan my dependencies How O3 SCA works

CVE-2006-3918 — 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-3918 in your dependencies?