CVE-2005-1125

NONECVSS 0.0Weaponized

0.0

Race condition in libsafe 2.0.16 and earlier, when running in multi-threaded applications, allows attackers to bypass libsafe protection and exploit other vulnerabilities before the _libsafe_die function call is completed.

CVSS v3: —
EG Score: —
EPSS: 91.5%
KEV: Not listed

Published

May 2, 2005

Last Modified

April 16, 2026

References (6)

cve@mitrehttp://www.overflow.pl/adv/libsafebypass.txt
cve@mitrehttp://www.securityfocus.com/archive/1/395999
cve@mitrehttp://www.securityfocus.com/bid/13190
af854a3a-2127-422b-91ae-364da2661108http://www.overflow.pl/adv/libsafebypass.txt
af854a3a-2127-422b-91ae-364da2661108http://www.securityfocus.com/archive/1/395999
af854a3a-2127-422b-91ae-364da2661108http://www.securityfocus.com/bid/13190

Data Freshness Timeline

(refreshed 9× in last 7d / 16× 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-05-29 13:40 UTCepss_batch
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:37 UTCepss_batch
2026-05-26 13:41 UTCepss_batch
2026-05-26 13:41 UTCepss_batch
2026-05-24 16:42 UTCepss_batch
2026-05-22 21:15 UTCepss_batch
2026-05-21 22:38 UTCepss_batch
2026-05-20 22:36 UTCepss_batch
2026-05-20 22:36 UTCepss_batch
2026-05-20 11:20 UTCepss_batch
2026-05-20 11:20 UTCepss_batch
2026-05-18 21:29 UTCepss_batch

Publicly available exploits

(2 references)

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

GitHub PoCtagatac/libsafe-CVE-2005-1125
First seen Oct 4, 2014
Libsafe - Safety Check Bypass Vulnerability (Proof of Concept Exploit & Time Randomization to Thwart It)
Open source ↗
Exploit-DBEDB-25429✓ verified
First seen Apr 15, 2005
Libsafe 2.0 - Multi-threaded Process Race Condition Security Bypass
Open source ↗

Frequently asked(4)

What is CVE-2005-1125?

CVE-2005-1125 is a none vulnerability published on May 2, 2005. Race condition in libsafe 2.0.16 and earlier, when running in multi-threaded applications, allows attackers to bypass libsafe protection and exploit other vulnerabilities before the libsafedie function call is completed.

When was CVE-2005-1125 disclosed?

CVE-2005-1125 was first published in the National Vulnerability Database on May 2, 2005, 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-2005-1125 actively exploited?

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

How do I remediate CVE-2005-1125?

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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2005-1125

Explore →

Is Your Infrastructure Affected by CVE-2005-1125?

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

Start Free Scan →Browse All CVEs

CVE-2005-1125

📅 Published

🔄 Last Modified

🔗 References (6)