# CVE-2026-8304: Information Disclosure in TUBITAK BILGEM's Pardus About

> Attackers can access sensitive information due to missing authorization checks in the Pardus About application.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Sep 2026
- **Updated:** 11 Sep 2026
- **Also known as:** GHSA-6rg9-qq5j-wggv

## What is CVE-2026-8304?

CVE-2026-8304 is a medium-severity missing authorization vulnerability in TUBITAK BILGEM Software Technologies Research Institute Pardus About, published on 11 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Missing Authorization vulnerability in TUBITAK BILGEM Software Technologies Research Institute Pardus About allows Exploiting Incorrectly Configured Access Control Security Levels.

This issue affects Pardus About: from 1.2.1 before 1.2.5.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-8304 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-8304 is a medium-severity missing authorization vulnerability in TUBITAK BILGEM Software Technologies Research Institute Pardus About, published on 11 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-8304 in the wild and no public exploit code.

Affected product: TUBITAK BILGEM Software Technologies Research Institute Pardus About. 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-8304/ (Markdown: https://insights.sbomify.com/CVE-2026-8304/index.md)
```

## Sources

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

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