CVE-2006-1542

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

A fix is available — apply it.

Stack-based buffer overflow in Python 2.4.2 and earlier, running on Linux 2.6.12.5 under gcc 4.0.3 with libc 2.3.5, allows local users to cause a "stack overflow," and possibly gain privileges, by running a script from a current working directory that has a long name, related to the realpath function. NOTE: this might not be a vulnerability. However, the fact that it appears in a programming language interpreter could mean that some applications are affected, although attack scenarios might be limited because the attacker might already need to cross privilege boundaries to cause an exploitable program to be placed in a directory with a long name; or, depending on the method that Python uses to determine the current working directory, setuid applications might be affected.

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

Published

March 30, 2006

Last Modified

April 16, 2026

References (8)

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhn_solaris_bootstrap_5_1_1_3-0:1-02008-08-13redhat
redhatrhn_solaris_bootstrap_5_0_2_3-0:1-02008-06-30redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

All Vendor Advisories

(3)

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.

Data Freshness Timeline

(refreshed 6× in last 7d / 29× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-13 22:25 UTCEPSS rescore
  2. 2026-07-13 06:07 UTCEPSS rescore
  3. 2026-07-13 06:07 UTCEPSS rescore
  4. 2026-07-11 08:22 UTCEPSS rescore
  5. 2026-07-09 19:03 UTCEPSS rescore
  6. 2026-07-08 15:09 UTCEPSS rescore
  7. 2026-07-06 02:19 UTCEPSS rescore
  8. 2026-07-06 02:19 UTCEPSS rescore
  9. 2026-07-04 06:26 UTCEPSS rescore
  10. 2026-07-02 14:00 UTCEPSS rescore
  11. 2026-07-01 15:01 UTCEPSS rescore
  12. 2026-06-27 03:04 UTCEPSS rescore
  13. 2026-06-25 13:46 UTCEPSS rescore
  14. 2026-06-24 14:01 UTCEPSS rescore
  15. 2026-06-24 14:01 UTCEPSS rescore
  16. 2026-06-23 21:29 UTCEPSS rescore
  17. 2026-06-23 21:29 UTCEPSS rescore
  18. 2026-06-22 14:22 UTCEPSS rescore
  19. 2026-06-21 01:56 UTCEPSS rescore
  20. 2026-06-19 19:22 UTCEPSS rescore
  21. 2026-06-19 19:22 UTCEPSS rescore
  22. 2026-06-18 17:49 UTCEPSS rescore
  23. 2026-06-18 17:49 UTCEPSS rescore
  24. 2026-06-17 17:49 UTCEPSS rescore
  25. 2026-06-17 17:49 UTCEPSS rescore
Show 47 more
  1. 2026-06-16 17:49 UTCEPSS rescore
  2. 2026-06-16 17:49 UTCEPSS rescore
  3. 2026-06-15 17:44 UTCEPSS rescore
  4. 2026-06-14 23:13 UTCEPSS rescore
  5. 2026-06-13 22:56 UTCEPSS rescore
  6. 2026-06-12 23:08 UTCEPSS rescore
  7. 2026-06-11 13:55 UTCEPSS rescore
  8. 2026-06-10 22:14 UTCEPSS rescore
  9. 2026-06-10 13:17 UTCEPSS rescore
  10. 2026-06-07 15:21 UTCEPSS rescore
  11. 2026-06-06 13:44 UTCEPSS rescore
  12. 2026-06-06 13:44 UTCEPSS rescore
  13. 2026-06-05 22:43 UTCEPSS rescore
  14. 2026-06-05 06:07 UTCEPSS rescore
  15. 2026-06-05 06:07 UTCEPSS rescore
  16. 2026-06-04 13:09 UTCEPSS rescore
  17. 2026-06-04 13:09 UTCEPSS rescore
  18. 2026-06-02 20:10 UTCEPSS rescore
  19. 2026-06-02 20:10 UTCEPSS rescore
  20. 2026-06-01 13:49 UTCEPSS rescore
  21. 2026-06-01 13:49 UTCEPSS rescore
  22. 2026-06-01 13:49 UTCEPSS rescore
  23. 2026-05-31 22:28 UTCEPSS rescore
  24. 2026-05-31 09:23 UTCEG score recompute
  25. 2026-05-31 09:23 UTCVendor advisory
  26. 2026-05-31 09:23 UTCGHSA enrichment
  27. 2026-05-31 00:13 UTCEPSS rescore
  28. 2026-05-31 00:13 UTCEPSS rescore
  29. 2026-05-31 00:13 UTCEPSS rescore
  30. 2026-05-29 13:40 UTCEPSS rescore
  31. 2026-05-28 13:42 UTCEPSS rescore
  32. 2026-05-28 13:42 UTCEPSS rescore
  33. 2026-05-27 13:37 UTCEPSS rescore
  34. 2026-05-27 13:37 UTCEPSS rescore
  35. 2026-05-26 13:41 UTCEPSS rescore
  36. 2026-05-26 13:41 UTCEPSS rescore
  37. 2026-05-26 07:16 UTCEPSS rescore
  38. 2026-05-26 07:16 UTCEPSS rescore
  39. 2026-05-24 16:42 UTCEPSS rescore
  40. 2026-05-22 21:15 UTCEPSS rescore
  41. 2026-05-22 21:15 UTCEPSS rescore
  42. 2026-05-21 22:38 UTCEPSS rescore
  43. 2026-05-20 22:36 UTCEPSS rescore
  44. 2026-05-20 22:36 UTCEPSS rescore
  45. 2026-05-20 11:20 UTCEPSS rescore
  46. 2026-05-20 11:20 UTCEPSS rescore
  47. 2026-05-18 21:29 UTCEPSS rescore

Publicly available exploits

(1 reference)

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

  • Exploit-DBEDB-1591✓ verified
    First seen Mar 18, 2006

    Python 2.4.2 - 'realpath()' Local Stack Overflow

    Open source ↗

Frequently asked(4)

What is CVE-2006-1542?
CVE-2006-1542 is a none vulnerability published on March 30, 2006. Stack-based buffer overflow in Python 2.4.2 and earlier, running on Linux 2.6.12.5 under gcc 4.0.3 with libc 2.3.5, allows local users to cause a "stack overflow," and possibly gain privileges, by running a script from a current working directory that has a long name, related to the realpath…
When was CVE-2006-1542 disclosed?
CVE-2006-1542 was first published in the National Vulnerability Database on March 30, 2006, with the most recent update on April 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2006-1542 actively exploited?
CVE-2006-1542 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 57.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
How do I remediate CVE-2006-1542?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2006-1542, 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-2006-1542

Explore →

Is Your Infrastructure Affected by CVE-2006-1542?

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

Start Free Scan →Browse All CVEs