What is CVE-2008-3914?

CVE-2008-3914 is a none vulnerability published on September 11, 2008. Multiple unspecified vulnerabilities in ClamAV before 0.94 have unknown impact and attack vectors related to file descriptor leaks on the "error path" in (1) libclamav/others.c and (2) libclamav/sis.c.

When was CVE-2008-3914 disclosed?

CVE-2008-3914 was first published in the National Vulnerability Database on September 11, 2008, with the most recent update on April 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2008-3914 actively exploited?

CVE-2008-3914 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 83.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

How do I remediate CVE-2008-3914?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2008-3914, 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.

CVE-2008-3914: NONE (CVSS 0)

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

CWE-200Exposure of Sensitive Information to an Unauthorized Actor

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.

Microsoft MSRCCVE-2008-39142020-10-25
Multiple unspecified vulnerabilities in ClamAV before 0.94 have unknown impact and attack vectors related to file descriptor leaks on the "error path" in (1) libclamav/others.c and (2) libclamav/sis.c.

Data Freshness Timeline

(refreshed 16× in last 7d / 20× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-06-02 20:10 UTCepss_batch
2026-06-02 20:10 UTCepss_batch
2026-06-01 13:49 UTCepss_batch
2026-06-01 13:49 UTCepss_batch
2026-06-01 13:49 UTCepss_batch
2026-05-31 22:28 UTCepss_batch
2026-05-31 22:28 UTCepss_batch
2026-05-31 00:13 UTCepss_batch
2026-05-31 00:13 UTCepss_batch
2026-05-30 20:24 UTCEG score recompute
2026-05-30 20:24 UTCVendor advisory
2026-05-30 20:24 UTCGHSA enrichment
2026-05-29 13:40 UTCepss_batch
2026-05-28 13:42 UTCepss_batch
2026-05-28 13:42 UTCepss_batch
2026-05-28 13:42 UTCepss_batch
2026-05-27 13:38 UTCepss_batch
2026-05-27 13:37 UTCepss_batch
2026-05-26 13:41 UTCepss_batch
2026-05-26 13:41 UTCepss_batch

CVE-2008-3914

Published

Last Modified

References (52)

Weakness Classification(1)

All Vendor Advisories

Data Freshness Timeline

Frequently asked(4)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2008-3914?

Same vendor

Same CWE

CVE-2008-3914

📅 Published

🔄 Last Modified

🔗 References (52)

Weakness Classification(1)

All Vendor Advisories

Data Freshness Timeline

❓ Frequently asked(4)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2008-3914?

🔗 Related CVEs(same vendor + same CWE)

Same vendor

Same CWE

Published

Last Modified

References (52)

Frequently asked(4)

Related CVEs(same vendor + same CWE)