# CVE-2026-12250: Sensitive Data Exposure in TUBITAK BILGEM's Pardus Domain Joiner


- **Severity:** High 7.9 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 5 Jul 2026
- **Updated:** 6 Jul 2026
- **Also known as:** GHSA-9pj6-hfxh-g9g8

## What is CVE-2026-12250?

CVE-2026-12250 is a high-severity vulnerability in TUBITAK BILGEM Software Technologies Research Institute Pardus Domain Joiner, published on 5 Jul 2026. 

### Official description

Invocation of process using visible sensitive information vulnerability in TUBITAK BILGEM Software Technologies Research Institute Pardus Domain Joiner allows Excavation.

This issue affects Pardus Domain Joiner: from 0.5.2 before 0.5.4.

Weakness: CWE-214 (Invocation of Process Using Visible Sensitive Information)

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


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

No fix has been published for CVE-2026-12250 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-12250 being exploited?

There is no known exploitation of CVE-2026-12250 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-12250 and fix it if it is affected.

What it is: CVE-2026-12250 is a high-severity vulnerability in TUBITAK BILGEM Software Technologies Research Institute Pardus Domain Joiner, published on 5 Jul 2026. 
Exploitation: There is no known exploitation of CVE-2026-12250 in the wild and no public exploit code.

Affected product: TUBITAK BILGEM Software Technologies Research Institute Pardus Domain Joiner. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-12250/ (Markdown: https://insights.sbomify.com/CVE-2026-12250/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-12250
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-12250
- OSV: https://osv.dev/vulnerability/CVE-2026-12250

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-12250/
Summaries are generated and may contain mistakes; the official description above is the record.