# CVE-2026-92606: TOCTOU Race Condition in TÜBİTAK BİLGEM's Pardus MyComputer

Status: published. Published: 2026-11-09. Updated: 2026-11-09.

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.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- TÜBİTAK BİLGEM Software Technologies Research Institute / Pardus MyComputer: ≥ 0.8.0; < 0.8.1 (affected, semver). Source: CNA: TR-CERT

## Severity and prioritization

- CVSS 3.1: 6 (medium); CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:N/I:H/A:H; source: CNA: TR-CERT

- CISA KEV: No listing in collected sources

- EPSS: Not available

- SSVC: Not available

- Weaknesses: CWE-367

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://siberguvenlik.gov.tr/guvenlik-bildirimleri/detay/tr-26-1485 (CNA: TR-CERT; government-resource)

## Provenance

- CNA: TR-CERT: https://www.cve.org/CVERecord?id=CVE-2026-92606; retrieved 2026-11-09; source updated 2026-11-09

Revision: a485a815aeb93cfc1a73644bb1f7c4fd7028a0d0e9da43e2317aef45b510da69

Canonical: https://y2.dev/cve/CVE-2026-92606

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.