TOCTOU Race Condition in TÜBİTAK BİLGEM's Pardus MyComputer
- Exploited
- Public exploit code, no confirmed attacks
- Fix
- Fixed in 0.8.1
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 0.8.1.
- Last modified
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.07% · 0th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 28/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- 1 proof of concept on GitHub
Summary
The TOCTOU race condition in TÜBİTAK BİLGEM's Pardus MyComputer lets a local attacker with low-privilege access corrupt data or disrupt the system by exploiting timing gaps between a check and its use. Exploiting it requires a victim to take an action, and the attack is not known to be in use.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
Time-of-check time-of-use (TOCTOU) race condition vulnerability in TÜBİTAK BİLGEM Software Technologies Research Institute Pardus MyComputer allows Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions.
This issue affects Pardus MyComputer: from 0.8.0 before 0.8.1.
cve.now Index
- Exploitation22/40Public exploit on Exploit-DB or GitHub · Unknown: No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity6/10CVSS 6.0
- No patch0/5No signal
What would change the score
- Would score about 61 if added to CISA KEV
- Would score about 56 if CISA's SSVC rates exploitation active
- Would score about 50 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 0.8.1.
Timeline
- CVE published
- First seen by cve.now
- Exploit code on GitHub
ozcanpng/CVE-2026-92606
Affected versions
- TÜBİTAK BİLGEM Software Technologies Research Institute Pardus MyComputer
From 0.8.0 · fixed in 0.8.1
Evidence 2
- Exploit
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-92606
Is CVE-2026-92606 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. Public exploit code exists (a proof of concept on GitHub).Source: cve.now feed data
Which versions are affected by CVE-2026-92606?
Pardus MyComputer: from 0.8.0 before 0.8.1.Source: cve.now feed data
How do I fix CVE-2026-92606?
Upgrade to a fixed version: 0.8.1.Source: cve.now feed data