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 version has been published for CVE-2006-3918 yet. Monitor the advisory for updates, apply mitigations recommended by the vendor, and use O3 Security to track when a fix becomes available in your stack.

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 91.4%, 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.

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.

CVE-2006-3918: Cross-Site Scripting

EPSS Exploitation Probability

via FIRST.org ↗

91.4%probability of exploitation in next 30 days

Very High Risk100th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

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.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is CVE-2006-3918 in your stack?

O3 detects CVE-2006-3918 across dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works