cve.bz

CVE-2006-5178 php php: Race Condition

no score yetExploitEPSS 0.7%

php php: no CVSS score yet. EPSS 0.7% estimated probability of exploitation activity in the next 30 days.

On this page
Race condition in the symlink function in PHP 5.1.6 and earlier allows local users to bypass the open_basedir restriction by using a combination of symlink, mkdir, and unlink functions to change the file path after the open_basedir check and before the file is opened by the underlying system, as demonstrated by symlinking a symlink into a subdirectory, to point to a parent directory via .. (dot dot) sequences, and then unlinking the resulting symlink.
EPSS
0.7% (unchanged from 0.7% a week ago; 0.7% 30 days ago) estimated probability of exploitation activity in the next 30 days; 52nd percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization (Race Condition)
OWASP Top 10
A06:2025 Insecure Design
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2006-5178 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2006-5178?via=ask-ai-copy and https://cve.bz/cve/CVE-2006-5178?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2006-5178 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
php:phpthrough 5.1.6
php:php4.0
php:php4.0.1
php:php4.0.1:patch1
php:php4.0.1:patch2
php:php4.0.2
php:php4.0.3:patch1
php:php4.0.4
php:php4.0.5
php:php4.0.6
php:php4.0.7
php:php4.0.7:rc1
php:php4.0.7:rc2
php:php4.0.7:rc3
php:php4.1.0
php:php4.1.1
php:php4.1.2
php:php4.2
php:php4.2.0
php:php4.2.1
php:php4.2.2
php:php4.2.3
php:php4.3.0
php:php4.3.1
php:php4.3.2
php:php4.3.3
php:php4.3.4
php:php4.3.5
php:php4.3.6
php:php4.3.7
php:php4.3.8
php:php4.3.9
php:php4.3.10
php:php4.3.11
php:php4.4.0
php:php4.4.1
php:php4.4.2
php:php4.4.3
php:php4.4.4
php:php5.0:rc1
php:php5.0:rc2
php:php5.0:rc3
php:php5.0.0
php:php5.0.1
php:php5.0.2
php:php5.0.3
php:php5.0.4
php:php5.0.5
php:php5.1.0
php:php5.1.1
php:php5.1.2
php:php5.1.3
php:php5.1.4
php:php5.1.5

Public exploits

Attack patterns (CAPEC)

  • CAPEC-26 Leveraging Race Conditions Likelihood: High · Severity: High
  • CAPEC-29 Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON