How severe is CVE-2006-2458?

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

Which packages are affected by CVE-2006-2458?

CVE-2006-2458 affects the following packages: extractor (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2006-2458?

The records we use list no patched version of extractor for CVE-2006-2458. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

How do I detect CVE-2006-2458 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for extractor, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

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

Stop feeding it untrusted input: reject or quarantine files and payloads from unverified sources until you can upgrade, restrict accepted formats to the ones you actually need, and run the parsing or decoding step in a least-privileged sandbox or short-lived worker so a crash or corrupted read cannot reach the rest of the process.

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

Yes. There are 3 known exploit references for CVE-2006-2458, including 1 documented proof-of-concept exploit on Exploit-DB and 2 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-2458?

CVE-2006-2458 has an EPSS (Exploit Prediction Scoring System) score of 9.2%, placing it in the 95th 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. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

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

CVE-2006-2458 was published on May 18, 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.

🐍 PyPI

Not in CISA KEV

CVE-2006-2458 — extractor

CVE-2006-2458 is a remote code execution vulnerability in extractor. 3 public exploit or proof-of-concept references are indexed, so weaponization risk is real. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Libextractor multiple heap-based buffer overflows

Also known asGHSA-f836-7jqw-3684PYSEC-2006-4

Published

May 18, 2006

Updated

Apr 10, 2026

Affected

1 pkg

Patched

See advisory

Exploits

3 known

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

EPSS Exploitation Probability

via FIRST.org ↗

9.2%probability of exploitation in next 30 days

Lower Risk+0.21%

Lower risk than most CVEs95th percentile — riskier than 95% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

🐍extractor

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Multiple heap-based buffer overflows in Libextractor 0.5.13 and earlier allow remote attackers to execute arbitrary code via (1) the asf_read_header function in the ASF plugin (plugins/asfextractor.c), and (2) the parse_trak_atom function in the QT plugin (plugins/qtextractor.c).

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`extractor`	all versions	No fix

Affected Products

1 product · 1 configurations

Application

libextractorlibextractor

1 version

0.5.13

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-1801dosmultiple✓ Verified

libextractor 0.5.13 - Multiple Heap Overflows (PoC)

by Luigi Auriemma · May 17, 2006

Exploit-DB Source

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for extractor, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of extractor for CVE-2006-2458. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
Stop feeding it untrusted input: reject or quarantine files and payloads from unverified sources until you can upgrade, restrict accepted formats to the ones you actually need, and run the parsing or decoding step in a least-privileged sandbox or short-lived worker so a crash or corrupted read cannot reach the rest of the process.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2006-2458 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works