CVE-2009-1071

NONECVSS 0.0Weaponized
0.0
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No confirmed exploitation signals yet
CISA-KEV: Not listedEPSS: 6%CVSS: Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Stack-based buffer overflow in Icarus 2.0 allows remote attackers to cause a denial of service (application crash) or execute arbitrary code via a crafted Portable Game Notation (.pgn) file.

CVSS v3
EG Score
0.0(none)
EPSS
92.5%
KEV
Not listed

Published

March 26, 2009

Last Modified

April 23, 2026

Weakness Classification(1)

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

Publicly available exploits

(2 references)

Working exploit code is in the public domain (2 Exploit-DB entries). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-9628✓ verified
    First seen Sep 10, 2009

    Icarus 2.0 - '.pgn' Universal Local Buffer Overflow (SEH)

    Open source ↗
  • Exploit-DBEDB-8236✓ verified
    First seen Mar 18, 2009

    Icarus 2.0 - '.pgn' Local Stack Overflow (SEH)

    Open source ↗

Frequently asked(4)

What is CVE-2009-1071?
CVE-2009-1071 is a none vulnerability published on March 26, 2009. Stack-based buffer overflow in Icarus 2.0 allows remote attackers to cause a denial of service (application crash) or execute arbitrary code via a crafted Portable Game Notation (.pgn) file.
When was CVE-2009-1071 disclosed?
CVE-2009-1071 was first published in the National Vulnerability Database on March 26, 2009, 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-2009-1071 actively exploited?
CVE-2009-1071 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 92.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
How do I remediate CVE-2009-1071?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2009-1071, 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.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2009-1071

Explore →

Is Your Infrastructure Affected by CVE-2009-1071?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.